On 9/1/2017 11:00 AM, Ken Brown wrote:
On 5/31/2017 6:50 AM, Jon Turney wrote:
What remains to be done:
- I've dodged a lot of the UI issues: If the solver reports problems,
all that
can be done is accept the default solution or cancel. This possibly
isn't a
big problem until we have a package set which can contain problems...
- We had a very poor UI for showing what will actually be done
(combine in
your head the "Pending" view with packages listed in the text on the
PrereChecker page), and this removes part of that
- As implemented, selecting "Current" overrides "Keep". This is
wrong, and a
change from current behaviour, but is probably a symptom of some deeper
confusion in the picker UI I'm not sure how to address
There are also some issues involving the treatment of test releases:
- It's not possible to install a test release of a package without
clicking the global Test button. But then you have to manually choose
Keep for all the package where you don't want the test release.
- Once a test release is installed, selecting Reinstall will downgrade
the package if the global Test button is not pressed. Presumably this
is because the test release has become invisible, since its repo has
been disabled. But I haven't checked carefully to see exactly what's
going on.
- I found some glitches involving SHA512 sums of test releases. It's
probably not worth pursuing this until the handling of test releases is
redone.
I fixed the last two problems, which turned out to have nothing to do
with the way test releases are handle. So all that's left of my three
issues is the first one, which is just a UI annoyance.
I don't think it makes sense for me to send further patches here.
Instead, I'll fork Jon's GitHub repo and continue to try to make
improvements.
Ken
