[Pkg-octave-devel] Slave update-alternatives [was: Re: Bug#383149: tried purging then reinstalling octave2.9 package]

Rafael Laboissiere rafael at debian.org
Thu Aug 17 09:11:45 UTC 2006

[moving to pkg-octave-devel]

* John W. Eaton <jwe at bevo.che.wisc.edu> [2006-08-17 04:13]:

> I have an up-to-date "testing" system and I installed Octave 2.9.7 with
>   apt-get update
>   apt-get -t unstable octave2.9{,-{headers,info,doc}}
> and then ran
>   update-alternatives --config mkoctfile
>   update-alternatives --config octave
>   update-alternatives --config octave-bug
>   update-alternatives --config octave-config
>   update-alternatives --config octave-depends
> BTW, why do I have to run all these commands?  I think it would be
> more friendly if running "update-alternatives --config octave" would
> take care of the rest automatically so they would all stay in sync.

One possibility would be to make the mkoctfile, octave-bug,
octave-config, and octave-depends alternatives slaves of the octave
alternative (in the same way the man pages are currently slaves of the
executables).  However, this would not work because these programs are in
different packages (octave and octave-bug in octave2.* and the rest in

We could make octave-bug slave of octave, but among mkoctfile,
octave-config, and octave-depends, which one should be the master?


More information about the Pkg-octave-devel mailing list