Fabrizio Polacco <fpolacco@icenet.fi> writes: > Christian Schwarz wrote: > > > > (a) make dpkg-perl `Essential' > > (b) make the package `Pre-Depend' on dpkg-perl > > (c) include dpkg-perl's code in the preinst script itself > > > > (a) has the problem that just tagging dpkg-perl `Essential' will not > > guarantee that dpkg-perl is installed (it's just "guaranteed" that > > it is not removed after it has been installed once) [..] > > That's why I suggest to implement (b) now. Since making a package > > Pre-Depend on another pages requires approval by the people on > > debian-devel, I officially request now to allow the > > > > tetex-* packages to `Pre-Depend' on dpkg-perl > > > > My 10penniä suggestion: > > Implement both a) and b) now. > > a) is the right_thing(tm) to do; > b) to solve tetex problem (thus only tetex should do that). > > Later (the sooner, the best), when one essential package will be > updated, simply put a depends: dpkg-perl on it (you will need to do > this also for perl-base, which will be essential too). > This will ensure that the essential package will be installed even on > systems that hasn't tetex (like mine). good idea. What about (mis)using libc6 for this purpose!? Every new/upgrading system will upgrade libc6 -> every system gets the essential dpkg-perl ;-) Bye Christian -- Christian Leutloff, Aachen, Germany leutloff@sundancer.oche.de http://www.oche.de/~leutloff/ Debian GNU/Linux 1.3.1! Mehr unter http://www.de.debian.org/
Attachment:
pgpFrKXM1VeqZ.pgp
Description: PGP signature