Setup.exe snapshot

Setup.exe snapshot

[Robert Collins]

I've placed a new snapshot of setup.exe at
http://www.cygwin.com/setup-snapshots.

Any commentary is welcome, with the caveat that duplicates aren't
interesting - no not even to guage the popularity or impact of a
problem. Triage occurs after inital analysis.

Firstly, the known bugs:
* The chooser can be a little funny updating.
* There is still no trivial way to 'install everything'.

Now for the list of recently accomplished things.
* Downloading will continue past errors, presenting the errors after all
downloads have been attempted - this aids unattended downloading.
* Multiple mirrors can be used in parallel. (use shift-click or
control-click).
* Dependencies will only trigger installation of a package - they won't
force an upgrade of an installed package. (with the caveat that in the
future versioned dependencies may force upgrades).
* Skip shows up for non installed packages, keep for installed packages
(consistently).
* The order of package versions when clicking the spin control is more
consistent (selected radio button (prev/curr/test)->source only (only if
the package is installed) ->oldest version...(skip version of radio
button)...->
newest version->uninstall->keep/skip->start again. The behaviour of the
src tickbox is more predicatable as well.
* Gary R Van Sickle has contributed an overhaul of the windowing code
that should fix the front/bottom annoyance with setup.

Hopefully this setup will become the released version in the near
future - so lets hear what you think!

Rob


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Setup.exe snapshot

[Christopher Faylor]

On Sun, Dec 23, 2001 at 11:59:33PM +1100, Robert Collins wrote:
>* Dependencies will only trigger installation of a package - they won't
>force an upgrade of an installed package. (with the caveat that in the
>future versioned dependencies may force upgrades).

Isn't this what has consistently gotten us into trouble?  Why not force
an update of a package if a package that depends on it is being upgraded?
This seems more intuitive to me.

Also, if we have no way to install all packages, then I think this new
release should be delayed.  We've been promising this for months.

If all that we need, however, is for upset to add things to a "Full"
category, which can be selected, I can do that.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Setup.exe snapshot

[Robert Collins]

> On Sun, Dec 23, 2001 at 11:59:33PM +1100, Robert Collins wrote:
> >* Dependencies will only trigger installation of a package - they
won't
> >force an upgrade of an installed package. (with the caveat that in
the
> >future versioned dependencies may force upgrades).
>
> Isn't this what has consistently gotten us into trouble?  Why not
force
> an update of a package if a package that depends on it is being
upgraded?
> This seems more intuitive to me.

We've had at lsat one bug report of the opposite, where someone was
running a custom file and had to continually select skip.

The way setup now works, when the chooser is presented, all installed
packages will be updated. If I take the following steps:
package foo, change to prev/kepp
unselected package bar, change to curr
then foo will be left at prev/keep.

BY DEFAULT, foo would have been upgraded. And if the user deselected
foo, then select bar, foo-current would be installed.

> Also, if we have no way to install all packages, then I think this new
> release should be delayed.  We've been promising this for months.
>
> If all that we need, however, is for upset to add things to a "Full"
> category, which can be selected, I can do that.

This is last thing in my list of features before doing a release.

Rob


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/