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

[Rafael Laboissiere <rafael@debian.org>]

* John W. Eaton <jwe@bevo.che.wisc.edu> [2006-08-17 14:03]:

> On 17-Aug-2006, Rafael Laboissiere wrote:
> 
> | We could make octave-bug slave of octave, but among mkoctfile,
> | octave-config, and octave-depends, which one should be the master?
> 
> Is there no way to update everything that happens to be installed, all
> at once?  I expect that most people who try this don't even realize
> that they would need run update-alternatives multiple times.  If they
> just do the octave config, then run mkoctfile, then try to use the
> resulting .oct file, it will fail.

Unless we unify the octave2.* and octave2.*-headers, I do not see how
this could be done in an error-safe way.  What about this:

    update-alternatives --config octave

for updating both octave and octave-bug, and:

    update-alternatives --config mkoctfile
    
for updating the rest?

-- 
Rafael