Re: autoup.sh & considerations on bail-out scripts
> The best thing to do IMO, is to make mountable and dpkg-ftp the standard
> methods, and do whatever is necessary to bring them up to scratch.
This seems like the best approach. dpkg -iGROEB considered harmful :-)
> dpkg-mountable works extremely well but doesn't yet understand
> pre-dependancies...it also needs support for pkg-order (which would
> solve the pre-dependancy problem).
We could do away with pre-dependency entirely when all installation
methods use package ordering.
> unfortunately, we're still going to need my autoup.sh script (or
> something very similar) to do the upgrade from bo to hamm - any
> improvements we make to dpkg methods wont be available on the target
> system until after the autoup stage of the upgrade has completed.
Not necessarily. dpkg-ftp and dpkg-mountable are both perl scripts.
They can be written to work with the perl in bo, and they could be
provided as separate packages. (dpkg-ftp already is). Then, we can
tell people to do "dpkg -i dpkg-ftp.deb" before upgrading, which is
much simpler than the autoup script.
Can this be done before the hamm release? I suspect that getting
package ordering right will be tricky, since a bo->hamm upgrade will
have to deal with versioned conflicts as well as dependencies. (The
libc5 development packages, and the old libraries.)
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: