From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: mingw64 packages
Date: Sat, 31 Oct 2020 13:27:54 -0600 [thread overview]
Message-ID: <b9b3b0fb-56e5-4d0b-dbe5-04214e24d050@SystematicSw.ab.ca> (raw)
In-Reply-To: <878sbmhhfp.fsf@Rainer.invalid>
On 2020-10-31 03:29, Achim Gratz wrote:
> Since I seem to pick up more of these… it is silly enough that you have
> to have two almost identical cygport files for the two architectures,
> but it does not make any sense to me to require these to be standalone
> git repositories. They share the sources and (most) patches with the
> Cygwin package of the same name and I don't really intend to track those
> changes manually across multiple submodules. So I'd like to keep these
> the same way I have done ZStandard: the Cygwin package and both MingW64
> packages in one Git repository.
The different git upstreams are the only reasons we have to keep separate
subdirectories for and copies of each of the mingw64-{x86_64,i686}-PKG files.
> That of course doesn't work in the CI as Scallywag gets its knickers in
> a twist when it sees more than one cygport file in the checkout. That
> looks like something that could hopefully be solved with either a YAML
> file or some more smarts on the Scallywag side?
We could use one PKG-mingw.cygport and vary the inheritance and packages using a
shell variable e.g.
$ MINGW_ARCH=... cygport ...
so the CI would always fail until it got smart enough! ;^>
--
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:[~2020-10-31 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 9:29 Achim Gratz
2020-10-31 19:27 ` Brian Inglis [this message]
2020-11-02 16:32 ` Yaakov Selkowitz
2020-11-02 20:33 ` 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=b9b3b0fb-56e5-4d0b-dbe5-04214e24d050@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).