[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Using debconf to choose among related packages.



Joey Hess <joey@kitenet.net> writes:

> >   db_metaget shared/window-manager owners
> >   for PKG in $RET; do
> >     dpkg-reconfigure -u $PKG;
> >   done

> Urk. I have my doubts that would work.

When I think about it I probally agree that it isn't the way to go (if
it would even work). It could have not so nice consequences when
someone tries to remove multiple packages using the same switch.

> When I write that example in the tutorial, I was assumming a
> tightly-knit set of packages, and just assumed that they could take care
> of setting things up to use whatever package was selected.

The actual problem right now is handling which alternativ the user
wants to use instead of letting the maintainers choose some, in some
cases random, priorities for update-alternatives. But I tried to
generalise to when one wanted to have different implemntation of same
service installed. Which packages is going to put it's stuff in
inetd.conf.

The update-alternatives problem could be solved by adding an option to
update-alternatives allowing it to force the use of a link from the
commandline. (something in betwen working in auto or manual mode)

Then a package should just do a "db_get shared/window-managers;
update-alternatives --use-link $RET" or something like it.

I will try to look at update-alternative tonight (GMT) and see how
much needs to be changed.

-- 
Peter



Reply to: