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: Building from source packages
Date: Mon, 23 May 2016 13:54:00 -0000	[thread overview]
Message-ID: <3e344b98-1f87-18f2-6b69-4a8d2772ebcb@dronecode.org.uk> (raw)
In-Reply-To: <k8bcjb97bglvo8o2i49rmaogpl90ljqq17@4ax.com>

On 13/05/2016 20:44, Andrew Schulman wrote:
>> * a few packages mistakenly use DEPENDS
>>
>> A few packages mistakenly use DEPENDS rather than DEPEND, which is
>> silently ignored
>
> I'm surprised none of them are mine.  It confuses me every time that I have to
> use REQUIRES, but DEPEND instead of DEPENDS. I have to go look it up again once
> or twice a month.
>
> To minimize the cognitive load on maintainers' brains, I humbly propose that
> cygport honor both REQUIRE and REQUIRES, and DEPEND and DEPENDS.
>
> Or it that's too ugly, make them both of the same form, i.e. REQUIRE and DEPEND.
> A one-time backwards-incompatible change that would make things easier in the
> future.

Yes, I get confused by it too, which is how I noticed this problem.  But 
I'm not sure how to fix this.

I wonder if it's possible to check the set of variables which exist 
after evaluating the cygport file, and warn if there are unexpected ones.

(Any existing uses of temporary variables inside a cygport file would 
have to be unset before it exits to avoid warning about them, but that 
seems a fair price to pay...)

  reply	other threads:[~2016-05-23 13:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-13 14:33 Jon Turney
2016-05-13 19:44 ` Andrew Schulman
2016-05-23 13:54   ` Jon Turney [this message]
2016-05-14  7:23 ` Achim Gratz
2016-05-18 16:05 ` Corinna Vinschen
2016-05-18 16:32 ` Marco Atzeri

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=3e344b98-1f87-18f2-6b69-4a8d2772ebcb@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).