Re: IMPORTANT: What can we do about the base package?
- To: firstname.lastname@example.org
- Subject: Re: IMPORTANT: What can we do about the base package?
- From: email@example.com (Kai Henningsen)
- Date: 04 Mar 1997 09:37:00 +0100
- Message-id: <6SD$cFKEcsB@khms.westfalen.de>
- In-reply-to: <6Rh6CAxEcsB@khms.westfalen.de>
firstname.lastname@example.org (Bruce Perens) wrote on 02.03.97 in <m0w1ODk-00IdU6C@golem.pixar.com>:
> I think the only solution right now is to do brain surgery on
> /var/lib/dpkg/status to forcibly remove the paragraph for the base
> package. Ugly, I'm sorry.
That's what I suspect, too.
So, unless Ian comes up with a better idea, I think we want to do
something like the following.
Dpkg experts: will this work?
1. Make sure that the packages that replace base really include everything
they should. I seem to recall that some directories didn't make it yet,
2. Make a new base package, version something like 99:obsolete, that pre-
depends on all the packages neded to replace base, thus making sure those
are installed before the preinst of the new base gets to run.
3. Have the preinst of the new package exchange the
/var/lib/dpkg/info/base file for either an empty file, or a file
containing only stuff that is _really_ obsolete (/usr/doc/base or stuff
4. Have the new base package be empty, not essential, and so on. Or maybe
even have the preinst tell people to purge the now-cleaned-up base and
5. Make sure this actually works before uploading the package.
6. Make sure this actually works before releasing 1.3.