public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: ASSI <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] wget
Date: Sun, 15 Nov 2020 08:36:13 +0100	[thread overview]
Message-ID: <87tutrqdg2.fsf@Otto.invalid> (raw)
In-Reply-To: <648ab3eb-4f71-b3a2-b90b-b0713d82ad07@SystematicSw.ab.ca> (Brian Inglis's message of "Sat, 14 Nov 2020 15:15:04 -0700")

Brian Inglis writes:
> I rebuilt with the original cygport updated minimally.

You're still supposed to search the configure log for any signs of it
not finding stuff you told it was available (like c-ares) and stuff that
you might not even now it wanted.

:-)

> This is one of those packages that advertises minimal dependencies and
> documents none AFAICT.

Everything older than about a year mostly looks like that.  Before
having the CI there wasn't a good way of figuring out the dependencies,
so almost nobody bothered with it.  It's still incomplete since the
dependencies pulled in by cygport will be assumed by the package (which
works only as long as these don't change).

> Is there a way of determining desirable, useful, or additional
> dependencies?

Usually the upstream documentation tells you their preferences.
Somtimes packages bundle dependencies, then you have to be careful to
direct the build to use the system libraries.  Additional dependencies
beyond those I tend to avoid.  I see you pulled in gnutls/nettle, I'd
rather use openssl unless upstream recommends against it.

Then you can look for the build specs on Linux distributions which
usually give you lots of clues (and often patches):

https://build.opensuse.org/package/view_file/openSUSE:Factory/wget/wget.spec?expand=1
https://src.fedoraproject.org/rpms/wget/blob/master/f/wget.spec

If in doubt, follow Fedora (like most other Cygwin packages).

> I found cygcares-2.dll was missing(!) from cygwin 32, so reinstalled
> it, and libnpth-devel was not installed in either arch, so installed
> those, added all the lib...-devel and tools dependencies to
> BUILD_REQUIRES, and all the relevant configure --with/out-... options,
> so now both arches build with only minor --version output differences.

Thank you.

I'm not really sure why you'd need libnpth and a bunch of other things.
You might want to add libattr-devel and see if xattr support gets
recognized.

> Is it sufficiently worth while to resolve with a release -2 package,
> as there may be no further upstream releases of the package, other
> than replacement by wget2?

Please re-release the fixed package so that both architectures are
equivalent.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

  reply	other threads:[~2020-11-15  7:36 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 [this message]
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
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=87tutrqdg2.fsf@Otto.invalid \
    --to=stromeko@nexgo.de \
    --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).