[Pkg-octave-devel] Re: update-alternatives and Octave packages

[Colin Ingram]

On 2/13/06, Rafael Laboissiere <rafael at debian.org> wrote:
> * Colin Ingram <synergizedmusic at gmail.com> [2006-02-12 03:44]:
>
> > > its pretty rough and incomplete but how about something like this:
> > >
> > a more complete version
>
> Your script looks good, thanks.  I will give it a try when time permits.
>
> How are we going to cope with update-alternatives --remove?
>

well that depends.  I noticed this weekend that you can have an
alternative install as a master link as well as a slave link.  For
example if you run my script on your system right now, it will set up
all the octave-pkg binaries as slaves to /usr/bin/octave but it will
not remove the master links for those binaries which will still exist
on your system.  IMHO this is not good.  I haven't tested to see what
happens if I try to update-alternatives on a master link which is a
slave to another binary yet but I will.  Does anyone see any benefit
to having your system set up like that?

To answer the question, we will have to add some code to this script
that ensures that none of the slave binaries are install as master
links.  (If we agree that having the system set up with both master
and slave links is undesirable) Then we can add some code that would
allow the script to be called with two arguments so it would be

octave-update-alternatives [--remove | --install] octave-pkg

on install it would do exactly what it does now, on remove it would do
exactly what it does now excluding the octave-pkg case from the
finally command.  This shouldn't be too difficult I will work on it
this week.  I'm going to commit what I have to
trunk/packages/octave/debian/in/ to facilitate the work.


> --
> Rafael
>
> _______________________________________________
> Pkg-octave-devel mailing list
> Pkg-octave-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-octave-devel
>