From: ASSI <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] gsasl libgsasl{7,-common,-devel,-doc} gsasl 2
Date: Mon, 18 Jul 2022 18:14:58 +0200 [thread overview]
Message-ID: <87a696jt31.fsf@Otto.invalid> (raw)
In-Reply-To: <b9f33e40-45ca-cedd-19a9-7e8440f1b624@SystematicSw.ab.ca> (Brian Inglis's message of "Sun, 17 Jul 2022 23:10:19 -0600")
Brian Inglis writes:
> I'd like to release 1.10 which is ABI compatible, as a test release with
> libcurl4 depending on it (also mine), a lot of libraries depend on that,
> and a lot of packages depend on those; try:
>
> $ cygcheck-dep -qSN libgsasl7 | less
>
> Release 2.0 jumps to libgsasl18, so that should probably be released as
> gsasl2/libgsasl2-{common,-devel,-doc}, and libcurl4 built and test
> released with that?
>
> Should the new library stay as libgsasl18 or be named libgsasl2_18?
No, at least it doesn't appear that upstream plans to support both
branches going forward.
At the moment no major distribution seems to package 2.0.1, but you can
glean what Debian is doing for their next release:
https://packages.debian.org/sid/source/gsasl
I would suggest keeping 1.10 current until at least two major distros
have switched.
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
prev parent reply other threads:[~2022-07-18 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 5:10 Brian Inglis
2022-07-18 11:43 ` Marco Atzeri
2022-07-18 15:18 ` Brian Inglis
2022-09-29 6:49 ` gsasl 2 libgsasl{18,-common,-devel,-doc} Brian Inglis
2022-09-30 12:39 ` Jon Turney
2022-09-30 17:55 ` Brian Inglis
2022-07-18 16:14 ` ASSI [this message]
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=87a696jt31.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).