Re: Essential virtual packages
Ben Collins wrote:
>
> 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
> >
<snip>
> > 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.
>
Ahh, ok, didnt think of that..
> As far as your situation, if you installed the same version as the
> original kernel, then it replaced that package.
>
I was more concerned that if the kernel installed by the kernel should
be listed and its not, then it could be considered a minor bug and
should be fixed.
Im still wondering about properties of virtual packages, another example
comes to mind, bash.
A shell is esential, but does it have to be bash ?
Could there be an esential virtual package called shell or something
that was provided by either bash, zsh, ash or any shell demed to be of
good enough quality, or is bash esential because there a bash specific
shell scripts in other esential packages ?
Glenn
Reply to: