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.]
