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: [ITP] wget2 - modern fast parallel file and recursive website downloader
Date: Wed, 8 Jul 2020 14:28:22 -0600	[thread overview]
Message-ID: <0a9a734c-e5f1-58a3-4947-2fef09271026@SystematicSw.ab.ca> (raw)
In-Reply-To: <964d4d23-25d4-bbb5-b054-f4bc5afece4b@SystematicSw.ab.ca>

On 2020-07-08 14:05, Brian Inglis wrote:
> wget2 is the successor of wget supplying a shared library API like curl to build
> a modern, fast, multi-threaded, parallel downloader using HTTP/2, HTTP
> compression and If-Modified-Since headers; see
> 
> 	https://gitlab.com/gnuwget/wget2
> 
> It is currently available on Arch, Debian/Ubuntu, openSUSE, Slackware:
> see
> 	https://pkgs.org/download/wget2
> 
> I could release the package as is with an exe and dll, but it should be built as
> separate bin, lib, devel, doc, and debuginfo packages, which I have never done
> before, so could do with some advice and assistance with the apporach required,
> which I based on curl, but that requires no script function overrides, and I
> believe this one may or I need some hints.
> 
> I have attached my base wget2.cygport which builds one monolithic package but
> contains comments for subpackage variables, plus comments showing other files
> which I think should be included in the subpackages, and both references to
> their locations in subpkg_CONTENTS and alterbative src_install script actions if
> cygport will not move the contents into the appropriate install directory.

Forgot to explain I also produced a summary of the files generated and/or
available for packaging under the triplet directory in manifest.list to my
previous email.

> I also need to understand how cyg...dll package numbering should work with this
> package: base zero or one and include or exclude the 2: libwget0, libwget1,
> libwget2_0, or libwget2_1, and how to get that generated?
> 
> Any advice, assistance, help, or hints from more experienced packagers would be
> welcome.
> 
> I can also update and release what may be the last patched version of the
> original wget 1.20.3 (currently 1.19.1) if Eric has no time, or ITA wget if he
> agrees.
> 
> I could also ITA curl from Yaakov as I use that and wget a lot in scripts and
> cron jobs.

-- 
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 IEC units and prefixes, physical quantities in SI.]

  reply	other threads:[~2020-07-08 20:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08 20:05 Brian Inglis
2020-07-08 20:28 ` Brian Inglis [this message]
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
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=0a9a734c-e5f1-58a3-4947-2fef09271026@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).