This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: [PATCH setup 00/10] Various setup patches
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin-apps at cygwin dot com
- Date: Wed, 03 Aug 2016 09:10:19 +0200
- Subject: Re: [PATCH setup 00/10] Various setup patches
- Authentication-results: sourceware.org; auth=none
- References: <20160802153037.125216-1-jon.turney@dronecode.org.uk>
Jon Turney writes:
> Track if a package was installed by user, or as a dependency
> Add an additional filter view, showing packages which were user picked
As a suggestion (and I won't have time for implementation help at the
moment): Please consider keeping /etc/setup/installed.db at version 2
and instead move the new-style database(s) to somewhere under
/var/setup. For some time we would have to generate both the old and
new databases from setup of course until everything has switched over to
the new locations. The format of the new database is up for discussion
I think, but besides the distinction between picked and non-picked I
think there should be a way to record version locks or preferences for
prev/curr/test.
I would also like to add checksums to the package lists, provided we can
find a way to ignore the changes due to rebasing, so it becomes easier to
audit an installation for changes.
> Reserve paths starting "." for package metadata
What did you envision here? In general I like the idea, but when we
start to have a structured package format I think we should move to some
other naming convention than .tar.xz, like .cyg or .cpm perhaps.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada