Re: Bug#47913: console-tools-libs: Priority required causes dselect problems on serial console machines
Matt Porter wrote:
>
> I still don't understand how dselect decides what packages it must
> automagically select. It seems it just marks everything that is required,
> standard or important as "install" How do I mark the console-* packages as
> "purge" or "hold" from a script?
>
This brings up something that has always torqued me about dselect.
Forgive my ranting, but I don't understand *why* dselect makes initial
selections at all. Thats the whole point of the task selector right?
If I wanted selections made for me then I would expect that to be the
place where it is done. As it stands now, I have to do this: "dpkg
--set-selections < selections-init" to unselect preselected packages I
don't want (selections-init is simply a text file containing my
selections). Its a pain to maintain the file since the default
selections change from time to time. If there were no default
selections, then I would only need to list desired packages in the
file. I have yet to find a proper way to remove all preselections. As
it stands now, I have to do twice the work for no reason other than bad
engineering.
--
Craig H. Block, Debian ia32 user
Linux 2.2.12 SMP i686 building CVS bf
Reply to: