On 2020-11-17 12:10, Achim Gratz wrote:
Brian Inglis writes:
I dug up some Debian, Fedora, and OpenSuSE patches, and added them to the
cygport.
OpenSuSE patches appear only to be available in their source package,
or online in their HTML page, for which I came up with a script to
grab a package's patch URLs, scrape those web pages for the patch
source, and convert from HTML to patch text. Do you know if there is
any way to access OBS patches as plain text?
Nothing that I've used before, but it wouldn't hurt to ask. There
obviously is some sort of an API that the osc CLI is using (I don't know
any details of that either), but how far that extends to plain HTTPS
REST requests I don't know.
This build avoids autoreconf (from Eric).
That is probably not urgent, but I'd check if it can be re-enabled. For
a while Cygwin had a too old autoconf version that would not work with
some packages tha twere using the newer ones, but that's no longer an
issue I'd think.
It would make sense to list DIFF_EXCLUDES in DISTCLEANFILES to avoid
them being packaged in the first place, as long as that did not break
the build.
So should I set DISTCLEANFILES to all the files *created* in the
following log extracts, and set DIFF_EXCLUDES to those for which
patches are created, or could more of each list be added to both?
In principle you should remove all files that are recreated anyway in
DISTCLEANFILES. Now, generated files showing up in the diff at all is a
likely deficiency in configure, as these should not be generated in the
source directory at all, I'd think. But getting a project that isn't
quite cleaned up for a separate build dir to put the files in the right
place (and later find them) can be quite an adventure.
Thanks again, that appears to be working after I tracked down one outlyer, and I
pushed the updates to run under CI, which now also builds and tests cleaner.
I will try defaulting src_compile to allow autoreconfig, and push if it works.
--
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.]
