[setup - the official Cygwin setup program] branch topic/fix-local-install, created. release_2.889-12-g1cf5673
jturney@sourceware.org
jturney@sourceware.org
Tue Mar 6 21:34:00 GMT 2018
at 1cf5673be9e020ace012ac5add6c6fcaa144954a (commit)
https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/setup.git;h=1cf5673be9e020ace012ac5add6c6fcaa144954a
commit 1cf5673be9e020ace012ac5add6c6fcaa144954a
Author: Jon Turney <jon.turney@dronecode.org.uk>
Date: Tue Mar 6 16:17:30 2018 +0000
Always give the fake root category the name 'All'
After we rearranged things in 0c539f7f, it's now too early to tell if we
have any packages or not.
The only thing about this category that is ever used is it's name, so we
don't actually need to use the real 'All' category here.
Saying 'No packages found' was never particularly helpful here, so just use
a fake category with the fixed name 'All'.
https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/setup.git;h=e8cc45429a153c2a815b63e894ea8f348e19cdbb
commit e8cc45429a153c2a815b63e894ea8f348e19cdbb
Author: Jon Turney <jon.turney@dronecode.org.uk>
Date: Tue Mar 6 14:56:40 2018 +0000
Fix packagemeta::ScanDownloadedFiles
packagemeta::scan clears the site list if the package was not found, and
packagemeta::ScanDownloadedFiles uses packageversion::accessible() to check
that.
Instead communicate via a return value
v2:
empty packages were always inaccessible, even though we returned early from
scan() without clearing the sites list, so return false in that case
https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/setup.git;h=19eee3c1e78288a2174b1269e2a843147ecda310
commit 19eee3c1e78288a2174b1269e2a843147ecda310
Author: Jon Turney <jon.turney@dronecode.org.uk>
Date: Tue Mar 6 15:48:03 2018 +0000
Update .gitignore
https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/setup.git;h=ec5992842a21868f542686031bc1f271d7037de7
commit ec5992842a21868f542686031bc1f271d7037de7
Author: Jon Turney <jon.turney@dronecode.org.uk>
Date: Fri Jan 19 15:36:03 2018 +0000
Add setup-minimum-version: to setup.ini
This allows setup.ini to require a certain setup version, rather than advise
a newer version when one is available.
Unfortunately, versions of setup prior to this one don't implement this, but
at least we have this going forward.
When we want to start using this, we can break backwards compatibility with
even older setup in a less clean way, simply by using setup.ini grammar that
they can't parse.
More information about the Cygwin-apps-cvs
mailing list