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: Re: [ITA] wget
Date: Tue, 17 Nov 2020 16:23:09 -0700	[thread overview]
Message-ID: <b943d4bf-d581-e834-1dd3-ab3a0a7355fb@SystematicSw.ab.ca> (raw)
In-Reply-To: <87a6vfu7dw.fsf@Rainer.invalid>

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

  reply	other threads:[~2020-11-17 23:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08 20:05 [ITP] wget2 - modern fast parallel file and recursive website downloader Brian Inglis
2020-07-08 20:28 ` Brian Inglis
2020-07-09 18:27   ` Marco Atzeri
2020-07-09 18:50     ` Yaakov Selkowitz
2020-07-10  1:38       ` Brian Inglis
2020-07-10  5:27         ` Marco Atzeri
2020-10-30 21:30           ` Brian Inglis
2020-10-30 21:34             ` Eric Blake
2020-10-30 21:57               ` [ITA] wget Brian Inglis
2020-10-31 12:50                 ` Marco Atzeri
2020-11-14 15:19                 ` Achim Gratz
2020-11-14 22:15                   ` Brian Inglis
2020-11-15  7:36                     ` ASSI
2020-11-15 17:32                       ` Brian Inglis
2020-11-16 17:23                         ` Achim Gratz
2020-11-16 21:35                           ` Brian Inglis
2020-11-17 19:10                             ` Achim Gratz
2020-11-17 23:23                               ` Brian Inglis [this message]
2020-11-18 14:23                               ` ASSI
2020-11-10  5:29           ` [ITP] wget2 - please review if anyone has time Brian Inglis
2020-11-24 21:06           ` [ITP] wget2 Brian Inglis
2020-11-27 17:57             ` Hamish McIntyre-Bhatty
2020-11-27 18:28               ` Brian Inglis
2020-11-30 14:51                 ` Hamish McIntyre-Bhatty
2020-11-30 18:29                   ` 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=b943d4bf-d581-e834-1dd3-ab3a0a7355fb@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).