From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Test: curl, libcurl{4, -devel, -doc}, mingw64-{x86_64, i686}-curl 7.86 (TEST)
Date: Wed, 02 Nov 2022 19:07:26 +0100 [thread overview]
Message-ID: <87mt99ut5t.fsf@Rainer.invalid> (raw)
In-Reply-To: <announce.20221101152414.58602-1-Brian.Inglis@SystematicSW.ab.ca> (Cygwin curl Maintainer's message of "Tue, 01 Nov 2022 15:24:14 -0600")
Cygwin curl Maintainer writes:
> The following *TEST* packages have been released in the Cygwin distribution:
>
> * curl 7.86
> * libcurl4 7.86
[…]
When building packages that depend on other new packages, these need to
be installed properly on the build system, i.e. have well-formed entries
in /etc/setup/installed.db and the corresponding package list file(s) so
that the dependencies can be determined by cygport. Otherwise you'd
have to explicitly list these dependencies when building the package,
but then there's the risk you'll forget it when the next update comes
around. This would have prevented the problem with the original release
and also ensure that this package can get installed without having to
select libgsasl18 manually for installation.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
next prev parent reply other threads:[~2022-11-02 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 21:24 Cygwin curl Maintainer
2022-11-02 18:07 ` Achim Gratz [this message]
2022-11-03 1:38 ` Lemures Lemniscati
[not found] ` <Y2MjCqOFZ0PqdN2G@xps13>
2022-11-03 6:43 ` Lemures Lemniscati
2022-11-03 7:36 ` ASSI
2022-11-03 17:48 ` Brian Inglis
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=87mt99ut5t.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@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).