public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] gsasl libgsasl{7,-common,-devel,-doc} gsasl 2
Date: Mon, 18 Jul 2022 13:43:37 +0200	[thread overview]
Message-ID: <8c52863b-9717-3442-11d6-2d8a951720a0@gmail.com> (raw)
In-Reply-To: <b9f33e40-45ca-cedd-19a9-7e8440f1b624@SystematicSw.ab.ca>

On 18.07.2022 07:10, Brian Inglis wrote:
> I'd like to adopt orphaned package gsasl as new versions have been 
> released.
> 
>      https://cygwin.com/packages/summary/gsasl-src.html
> 

all yours

> https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/gsasl.git
> 
> I've rebuilt current 1.8 and upgraded releases 1.8.1, 1.10, 2.0, and
> 2.0.1 for x86/i686 and x86_64 without any issues.
> The 2.0.1 build was run in GitHub Actions CI using the gsasl repo
> playground branch; see:
> 
>      https://cygwin.com/cgi-bin2/jobs.cgi?srcpkg=gsasl
> 
> and scallywag logs are at:
> 
>      https://github.com/cygwin/scallywag/actions/runs/2682310926
> 
> 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?

I would follow the name of the library.
If it is just cyggsasl-18.dll use libgsasl18

> How to rebuild libcurl4 with libgsasl2-devel using libgsasl{2_}18?

I suggest to avoid collision between version 1 and 2.
possibly moving away the old version and leaving in the usual place the 
last one

/usr/include/*.h -> /usr/include/gsasl1/*.h
usr/lib/libgsasl.dll.a usr/lib/gsasl1/libgsasl.dll.a


Regards
Marco

  reply	other threads:[~2022-07-18 11:43 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 [this message]
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 ` [ITA] gsasl libgsasl{7,-common,-devel,-doc} gsasl 2 ASSI

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=8c52863b-9717-3442-11d6-2d8a951720a0@gmail.com \
    --to=marco.atzeri@gmail.com \
    --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).