public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin@cygwin.com
Subject: Re: per-version hints proposal
Date: Thu, 01 Sep 2016 17:13:00 -0000	[thread overview]
Message-ID: <51b0e5e5-6556-69df-c631-3c26f5d2ce56@dronecode.org.uk> (raw)
In-Reply-To: <87mvjs4uq9.fsf@Rainer.invalid>

On 31/08/2016 20:13, Achim Gratz wrote:
> Jon Turney writes:
>>> calm will be changed so that:
>>>
>>> * The requires: line written in setup.ini will contain the union of the
>>> requires: from each pvr.hint
>>>
>>> * The sdesc:, ldesc:, category: and message: lines in setup.ini will be
>>> taken from the pvr.hint for the curr version
>
> I've not given this much more thought, but I think we should change the
> setup.ini syntax to allow different values for _all_ keys in a package
> for each version.

Yes, ultimately.

There's not much value until we have some functionality or UI which uses 
that, though, and changing setup.ini syntax like that is probably 
incompatible with older setup.

> The ones that are not in a specific section
> (i.e. where they are now, right after the package line) would just
> provide a default that gets used when there is no version-specific value
> provided in the corresponding section.  Calm could/should move such
> key/value pairs to the default when they are identical among the
> majority of versions, otherwise use those from the current version.

This seems perhaps a bit of a premature optimization.

The setup.ini will be compressed, so any redundancy between versions 
won't affect the file size much.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

           reply	other threads:[~2016-09-01 17:13 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <87mvjs4uq9.fsf@Rainer.invalid>]

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=51b0e5e5-6556-69df-c631-3c26f5d2ce56@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@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).