Re: Really unhappy with one dselect behavior...
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
that is the single most annoying thing about dselect, with the conflict
resolution screen that pops up *whenever* the selection has unmet
dependencies coming in distant second (because it's just a mild annoyance,
not actually harmful -- you don't lose data unless you get used to
hitting return at the resolution screen without looking). something
really needs to be done about it.
> ... but
> better than that would be to switch things so that dselect doesn't
> clobber the list of new packages on "selection" exit, but rather at
> the begin of the install run. This would make it much easier to go
> through the new packages in several sittings.
or better yet, not until the next update step. or maybe there should be
a different section for things that were new at the last update, but not
selected between then and the last install ("passed-over"? "semi-new"?),
so that you could do dselect in multiple stages and install after each
one (might be useful if you found one package you really wanted right
away, before you finish the selection of all the rest. probably doesn't
happen often but one instance comes to mind right away -- initial
installations).
- --p.
"Reasoning is partly insane." --Rush, "Anagram (for Mongo)"
PGP 5.0 key available at http://cif.rochester.edu/~phouchg/pgpkey.txt
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
Comment: Processed by Mailcrypt 3.5.1, an Emacs/PGP interface
Charset: noconv
iQA/AwUBNu2jjZ49M+7gJHRJEQJcEACePbUPkdxTZwQMk/8WtkcWAdTKPbYAoNuW
5ZIzAzZPVzXYllkLpaQzAxEk
=mgXp
-----END PGP SIGNATURE-----
Reply to: