Bug#479080: debian-policy: Policy '3.8 Essential packages' does not explain when/why essential is neccessary
On Fri, 6 Jun 2008 09:38:15 +0200, Bernhard R Link <brlink@debian.org> said:
> * Steve Langasek <vorlon@debian.org> [080605 19:04]:
>> This is not part of the rationale for a package's inclusion in
>> Essential, it's an effect of a package's inclusion in Essential.
>>
>> Packages should only be in the Essential set if they have to be there
>> to guarantee the operation of dpkg.
> I've experimented recently with some more minimal build chroots (even
> dropping some essential stuff), and I do not think that above matches
> the current situation.
I think I still stand by what I said:
>>> My understanding is that a package is Essential if without it is
>>> impossible to install any more packages to the system -- that is,
>>> the package is required for proper functioning of dpkg
on the system.
This remains true, if one is talking of a system, instead of
part of one hosted on another system providing most of the services. So
minimal chroots are out, when deciding whether a Package is Essential
or not.
manoj
--
You will be aided greatly by a person whom you thought to be
unimportant.
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Reply to: