public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Subject: Planned setup.ini changes for early 2018
Date: Wed, 10 Jan 2018 22:44:00 -0000	[thread overview]
Message-ID: <5e585f56-b4b1-753d-7ca8-0f7894194fa9@dronecode.org.uk> (raw)


* Add depends: to version descriptions

This is a version-specific list of required packages (as opposed to 
requires:, which is per-package, and contains the union of the 
dependencies for all versions).

I believe that historical setup versions will either ignore, or can 
handle depends: (just containing package names, without version 
relations) relatively sanely (see [1] et seq. for details).

* De-duplicate source archives

Source archives which are identical[2] between x86 and x86_64 will be 
moved to paths starting src/ in the release area.

Doing post-hoc de-duplication is unfortunate, but worthwhile given the 
potential size saving in mirrors (see [3] et seq.), until cygport can be 
taught how to make suitable source packages (which has several 
unresolved issues, also discussed at [3], [4] et seq.).

* Migrate from setup.hint to pvr.hint in release area

I also plan to migrate all remaining setup.hints to pvr.hints in the 
release area (setup.hint in uploads have been automatically migrated 
since [5]).

This should have no effect on the generated setup.ini, but enables some 
complexity (some of which isn't implemented properly, see [6]) to be 
removed from calm.

[1] https://cygwin.com/ml/cygwin-apps/2017-12/msg00020.html
[2] my current implementation considers two archives identical if they 
have an identical set of members, with identical contents. Permitted 
differences include the mtime, mode or owner of members.
[3] https://cygwin.com/ml/cygwin-apps/2017-04/msg00069.html
[4] https://cygwin.com/ml/cygwin-apps/2017-05/msg00012.html
[5] https://cygwin.com/ml/cygwin-apps/2017-11/msg00044.html
[6] https://cygwin.com/ml/cygwin-apps/2017-10/msg00123.html

             reply	other threads:[~2018-01-10 22:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 22:44 Jon Turney [this message]
2018-01-10 23:27 ` David Stacey
2018-01-13 17:21   ` Jon Turney
2018-01-11 17:55 ` Peter A. Castro
2018-01-12 15:48   ` Jon Turney
2018-01-12 18:13     ` Peter A. Castro
2018-01-13 17:22       ` Jon Turney
2018-01-11 18:30 ` Achim Gratz
2018-01-13 18:43   ` Achim Gratz
2018-01-13 18:35 ` Achim Gratz
2018-01-15 19:02   ` Jon Turney
2018-01-16 18:12     ` Achim Gratz
2018-01-22 23:13 ` Jon Turney
2018-01-23 18:30   ` Achim Gratz
2018-01-24 20:30     ` Jon Turney
2018-01-24 20:57       ` Achim Gratz
2018-01-28 15:07   ` Jon Turney
2018-03-01 16:01 ` Jon Turney
2018-03-01 16:39   ` Marco Atzeri
2018-03-01 17:02     ` Jon Turney
2019-05-30 14:08   ` Jon Turney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5e585f56-b4b1-753d-7ca8-0f7894194fa9@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).