From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] biosig [was: Re: newcomer issues when packaging biosig, stimfit, etc.]
Date: Tue, 18 Jan 2022 15:56:12 -0700 [thread overview]
Message-ID: <39e25058-5c5c-e2a9-7452-0a5b90ceee1e@SystematicSw.ab.ca> (raw)
In-Reply-To: <9aa0ab98-2270-0593-df1f-28bad20420f2@gmail.com>
On 2022-01-18 14:50, Alois Schlögl wrote:
> Am 1/18/22 um 06:32 schrieb Brian Inglis:
>> On 2022-01-17 14:44, Alois Schlögl wrote:
>>> Am 1/15/22 um 21:44 schrieb Achim Gratz:
>>>> Marco Atzeri writes:
>>
>>>>> add DIFF_EXCLUDES="Makefile" to avoid the artifact
>>
>>>> DISTCLEANFILES would be more appropriate it seems.
>>
>> DISTCLEANFILES is deleted immediately after downloading and unpacking
>> the *UPSTREAM* source:
>>
>> https://cygwin.github.io/cygport/src_prep_cygpart.html#robo112
>>
>> "A list of files to be deleted immediately upon unpacking sources,
>> relative to $S. This is intended to be used with buildsystem-generated
>> files which are incorrectly included in the source tarball."
>>
>>> I tried this (see attachment), but I'm not sure this is what you meant.
>>
>> DIFF_EXCLUDES is a list of files generated in $S not automatically
>> excluded from the source package:
>>
>> https://cygwin.github.io/cygport/pkg_pkg_cygpart.html#robo384
>>
>> "A list of file names, directory names, or glob patterns in $S which
>> will be excluded when creating the .src.patch file. This should be
>> used for files automatically generated in $S to avoid polluting the
>> patch.
>> NOTE
>> Files generated by various buildsystem infrastructures, such as
>> autoconf, automake, gettext, and libtool are already excluded
>> automatically and need not be listed here."
>> Add to DIFF_EXCLUDES the names of any files you see after the output
>> header:
>>
>>>>> Creating source patches
> Ok, thanks for these clear hints. I've now added these files as
> suggested. The revised version is attached.
> Moreover, I've removed (commented) all aspects for building of
> python-biosig bindings, in order not to delay the inclusion of Biosig in
> Cygwin.
> Is there anything else that need to be considered ?
CATEGORY is a *space* separated list in quotes.
Before SRC_URI and PATCH_URI normally comes:
HOMEPAGE=https://sourceforge.net/projects/biosig/files/
you don't need to add quotes for nonspaced strings.
You may also test your cygport and any other source patches and files
you require by creating and committing them into a local git repo named
the same as the package (preferably all lower case) and pushing to the
git-cygwin-packages playground repo and branch:
git push --set-upstream ssh://cygwin/git/cygwin-packages/playground.git
playground -f
which will submit the build to the Cygwin GitHub Action CI and print the
link for you to monitor the CI job, view the build logs for noarch, x86,
and x86_64, and download them.
--
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.]
next prev parent reply other threads:[~2022-01-18 22:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <99eff890-3d7f-7fa9-1f42-d8d611b92ded@gmail.com>
2022-01-08 17:41 ` newcomer issues when packaging biosig,stimfit, etc Marco Atzeri
2022-01-08 19:15 ` Marco Atzeri
2022-01-08 19:24 ` Marco Atzeri
[not found] ` <a3f8e657-1e1d-c582-2a07-806c6c03be02@gmail.com>
2022-01-12 5:47 ` Marco Atzeri
2022-01-12 6:16 ` Brian Inglis
2022-01-12 22:59 ` [ITP] biosig [was: Re: newcomer issues when packaging biosig, stimfit, etc.] Alois Schlögl
2022-01-14 10:09 ` Marco Atzeri
2022-01-14 21:48 ` Alois Schlögl
2022-01-15 18:01 ` Marco Atzeri
2022-01-15 20:44 ` Achim Gratz
2022-01-17 21:44 ` Alois Schlögl
2022-01-18 5:32 ` Brian Inglis
2022-01-18 21:50 ` Alois Schlögl
2022-01-18 22:56 ` Brian Inglis [this message]
2022-01-19 3:51 ` Brian Inglis
2022-01-20 20:48 ` Alois Schlögl
2022-01-21 12:53 ` Jon Turney
2022-01-16 22:13 ` Alois Schlögl
2022-01-22 17:52 ` Marco Atzeri
2022-01-25 23:50 ` Alois Schlögl
2022-01-26 4:52 ` Marco Atzeri
2022-01-26 22:47 ` 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=39e25058-5c5c-e2a9-7452-0a5b90ceee1e@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).