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: Re: residual setup.hint
Date: Tue, 04 Apr 2017 17:38:00 -0000	[thread overview]
Message-ID: <d4df834b-9d58-925e-ee14-1c31e9b4323b@dronecode.org.uk> (raw)
In-Reply-To: <305df537-3da2-fc5b-c546-3dd3c5a1c723@gmail.com>

On 04/04/2017 14:28, Marco Atzeri wrote:
> Not sure if "calm" is excluding them, but I noticed for some
> packages we have now an excess of "setup.hint" as all existing
> revision have their own package-revison.hint

These old setup.hint files should be benign, unless they are recording 
obsolete dependencies which aren't needed any more.

[...]
> Is a cleaning needed ?

Eventually, yes.

Unfortunately, a maintainer removing these files via '-setup.hint' is 
not permitted, as I haven't implemented it due to the complexity of 
determining if that is safe.

I've noted that there needs to be a migration plan for this (See [1])

I guess the first stage of which is to turn off uploads containing 
setup.hint (as generated by older versions of cygport), but I'm not sure 
we've reached that point in time, yet.

[1] https://cygwin.com/ml/cygwin-apps/2016-09/msg00025.html

  reply	other threads:[~2017-04-04 17:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 13:28 Marco Atzeri
2017-04-04 17:38 ` Jon Turney [this message]
2017-04-05 20:55   ` Marco Atzeri
2017-04-05 22:42     ` Jon Turney
2017-04-06  3:39       ` Marco Atzeri
2017-04-07 11:17         ` 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=d4df834b-9d58-925e-ee14-1c31e9b4323b@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).