From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from omta001.cacentral1.a.cloudfilter.net (omta001.cacentral1.a.cloudfilter.net [3.97.99.32]) by sourceware.org (Postfix) with ESMTPS id 336703858D28 for ; Thu, 29 Sep 2022 06:49:26 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 336703858D28 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=systematicsw.ab.ca Received: from shw-obgw-4004a.ext.cloudfilter.net ([10.228.9.227]) by cmsmtp with ESMTP id dbydouPPcS8WrdnMLo5gTy; Thu, 29 Sep 2022 06:49:25 +0000 Received: from [10.0.0.5] ([184.64.124.72]) by cmsmtp with ESMTP id dnMLodlMQlQu6dnMLovXyb; Thu, 29 Sep 2022 06:49:25 +0000 X-Authority-Analysis: v=2.4 cv=YfOuWidf c=1 sm=1 tr=0 ts=63353ff5 a=oHm12aVswOWz6TMtn9zYKg==:117 a=oHm12aVswOWz6TMtn9zYKg==:17 a=IkcTkHD0fZMA:10 a=w_pzkKWiAAAA:8 a=NEAV23lmAAAA:8 a=uYT-Tk0qkVT609LjNaIA:9 a=QEXdDO2ut3YA:10 a=4UoSMJil8JwA:10 a=sRI3_1zDfAgwuvI8zelB:22 Message-ID: <61cd6277-3665-2dd6-b75c-8fe7a7210c96@SystematicSw.ab.ca> Date: Thu, 29 Sep 2022 00:49:24 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.13.1 Reply-To: Cygwin Applications Subject: Re: gsasl 2 libgsasl{18,-common,-devel,-doc} Content-Language: en-CA To: Cygwin Applications References: <8c52863b-9717-3442-11d6-2d8a951720a0@gmail.com> Cc: Brian Inglis From: Brian Inglis Organization: Systematic Software In-Reply-To: <8c52863b-9717-3442-11d6-2d8a951720a0@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4xfBmDum2BOHzOdJSKHizTnrPjuFrK+kR3JZCtC1LucIMPHHgakyzsTsVhLpE4j4L4WoW4auxHt+n0i0BWHvEWAEMVYdafp4SLXGF2CoiLKd0FLYByEaJ4 rs6gidareCSRGIVszZVat9JWPV51jn9PZAZJLN3W/TayIPLSbes08XD05kgdkvfyYElUNU9IS3th5q4yG8SuIDrUbajT672o/nKZd6BlsvDtbcWx76g2bCY2 2S0DnwM0VQ+FwoSDAueA+w== X-Spam-Status: No, score=-1164.3 required=5.0 tests=BAYES_00,BODY_8BITS,KAM_DMARC_STATUS,KAM_LAZY_DOMAIN_SECURITY,NICE_REPLY_A,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 2022-07-18 05:43, Marco Atzeri wrote: > 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 Hi folks, [Please Reply All as ISP blocking Cygwin mail] It looks as if gsasl 2 is ABI 18 compatible with gsasl 1.10, so I am looking to release 2.2 as a continuation of the existing versions, and that is consistent with FreeBSD and Debian, where the developer appears to be among the package maintainers. One issue is that autoreconfig replaces the package provided gtk-doc.make with one from /usr/share/gtk-doc/data/gtk-doc*.make and they (all) need patched to build PDFs with DESTDIR builds. I handled this with local patches, added a src_patch_apply_hook to apply these for scallywag builds, and submitted patches upstream to the gsasl list and gtk-doc repo. The current orphaned gtk-doc cygport build seems to work automagically from the upstream tar(.xz) included in the source package, and I am too ignorant of Gnome, GTK, dblatex, TeX, etc., that I am uncomfortable adopting gtk-doc, as I have enough backlogged package updates. Suggestions for doing a non-maintainer update? -- 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 binary units and prefixes, physical quantities in SI.]