Steve Langasek <[EMAIL PROTECTED]> wrote:
> No, that's not what I said. The python-minimal package is designed to be
> used *as* an Essential package, not *by* Essential packages. Nothing,
> essential or not, should depend on it in Debian, whether or not
> python-minimal itself gets marked as Essential: yes. (As long as
> python-minimal is not essential, you don't depend on it because it shouldn't
> be installed without python; if python-minimal *is* essential, you don't
> depend on it because you don't declare dependencies on essential packages.)
I'm playing paranoid here, but why don't you want to declare
dependencies on essential packages? If the package ceases to be Essential at
some point in the future, some non-essential packages may still need it's
functionality, but without this relationship being tracked, the package
could easily disappear. Wouldn't it be better for the package database to
have as much information as possible on what uses what, essential or not?
Thanks,
Tyler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
