public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: [PATCH} cygport src_fetch.cygpart PATCH_URI doc addition
Date: Sun, 14 Nov 2021 07:39:18 -0700	[thread overview]
Message-ID: <af94c9c3-b412-3ad6-52c1-c8b7e73a24db@SystematicSw.ab.ca> (raw)
In-Reply-To: <87k0hb9iil.fsf@Otto.invalid>

[-- Attachment #1: Type: text/plain, Size: 747 bytes --]

On 2021-11-14 01:10, ASSI wrote:
> Jason Pyeron writes:
>> Not sure I understand this, that file is explicitly patched to
>> build. See: aide-0.17.3-1.cygwin.patch

> Give that patch file a different name (just changing the . before cygwin
> to a - would suffice) and add it to PATCH_URI in the cygport file
> instead.  ${PVR}.{cygwin,src}.patch files are special to cygport.

Wondered how that was being picked up and applied without being named in 
the .cygport. Suggested cygport doc patch attached.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

[-- Attachment #2: src_fetch.cygpart.patch --]
[-- Type: text/plain, Size: 565 bytes --]

From Achim Gratz: 
https://cygwin.com/pipermail/cygwin-apps/2021-November/041670.html

--- origsrc/cygport/lib/src_fetch.cygpart	2021-06-20 09:44:05.617763800 -0600
+++ src/cygport/lib/src_fetch.cygpart	2021-11-14 07:14:23.018207400 -0700
@@ -59,6 +59,8 @@
 #  their basenames to PATCH_URI.  This provides an easy way to carry
 #  Cygwin-specific patches forward between releases.
 #  NOTE
+#  ${PVR}.{cygwin,src}.patch files are special to cygport:
+#  they are automatically applied if present.
 #  See SRC_URI for details about URI handling in cygport.
 #****
 

  reply	other threads:[~2021-11-14 14:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30 14:34 [ITP] aide 0.17.3 Jason Pyeron
2021-09-29 14:27 ` Jason Pyeron
2021-09-30  0:07   ` Brian Inglis
2021-10-31 12:47   ` Jon Turney
2021-10-31 14:37     ` Jason Pyeron
2021-11-10 12:33       ` Jason Pyeron
2021-11-10 16:24         ` Brian Inglis
2021-11-12 12:48           ` Jason Pyeron
2021-11-12 16:49             ` Brian Inglis
2021-11-14  1:37               ` Jason Pyeron
2021-11-14  8:10                 ` ASSI
2021-11-14 14:39                   ` Brian Inglis [this message]
2021-11-14 12:49       ` Jon Turney
2021-11-14 16:36         ` Jason Pyeron
2021-11-14 17:00           ` Achim Gratz

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=af94c9c3-b412-3ad6-52c1-c8b7e73a24db@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).