Re: Essential virtual packages
On Sat, Aug 19, 2000 at 04:16:08PM +1000, Glenn McGrath wrote:
> Im trying to understand a few things relating to packaging... take the
> kernel for example
>
> I just did a fresh install of potato, and then installed my own kernel
> image built by kernel-package, dselect lists my custom kernel as being
> the only kernel-image installed, i cant see any reference to the
> original kernel image.
> Shouldnt both be the original kernel and my custom kernel be listed as
> being installed?
>
> According to my understanding from the policy manual the functionality
> provided by the virtual package kernel-image, which in my case is
> supplied by both the original and custom kernel should be both required
> and Essential...
>
> I cant find any details on the virtual package kernel-image except its
> name, do virtual packages have priorities and can they be marked
> essential ?
Kernel is not and essential package for two very specific reasons.
Firstly, the user might not wish to use a packaged kernel, and rely on
manually installed kernels. Secondly, it is very possible to not have a
kernel installed on the local system at all, like for network based
clients.
As far as your situation, if you installed the same version as the
original kernel, then it replaced that package.
--
-----------=======-=-======-=========-----------=====------------=-=------
/ Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \
` bcollins@debian.org -- bcollins@openldap.org -- bcollins@linux.com '
`---=========------=======-------------=-=-----=-===-======-------=--=---'
Reply to: