Mail Archives: cygwin-apps/2001/11/20/10:32:37
And, there are a couple of UI issues that need some help. If new
packages are defaulted to 'install', then #1 will already be solved.
However I think now that you've gone down the road of having all
packages default to 'skip' (excepting category=Base of course) you
should consider keeping it that way. My preference would be for newly
added/updated packages to be VISIBLE (without having to expand the
categories); but not default to install.
Here are the bugs I've noticed:
1: non-installed packages (aka newly added ones) used to default to
"install current".
The next choice in the revolving action list was "skip", followed by
(I think)
"install previous".
But now, they default to "skip", followed by "install previous", ...
This action needs to change so that Skip is follow by "install
current".
My preference here would actually be to keep "install previous" out
of this
list, and only allow installing previous if you click the "Prev"
radio button
at the top.
2: Category listings -- if I select a package (say curl) from one
category, that
requires another pkg (say OpenSSL) from a DIFFERENT category, AND if
the 2nd
category was not yet expanded: the 2nd package (openssl) appears all
by itself
underneath its category, and when I click the 2nd category's name to
show the
rest of the packages in it, it actually closes; I have to click a 2nd
time to
show all. My opinion - that first click on the 2nd category should
open the
full list under that category, rather than hiding the openssl
package.
Also, if you add "meta-packages"; what happens if I choose to install
"workstation",
but then I change my mind and want to switch to something else that
doesn't include
all the same packages; will the required dependancies deselect
themselves also?
--Kevin
- Raw text -