public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Cc: Christian Franke <Christian.Franke@t-online.de>
Subject: Re: [ITP] afflib 3.7.20-1
Date: Thu, 7 Mar 2024 06:43:57 +0100	[thread overview]
Message-ID: <CAB8Xom_r8Z50bvv3EOu6KDNYSV6h=hi4K78rRCpYsvhk-M9pqQ@mail.gmail.com> (raw)
In-Reply-To: <12d1c940-5f9b-4afd-d8de-12caa927e2fe@t-online.de>

On Wed, Mar 6, 2024 at 11:26 PM Christian Franke via Cygwin-apps  wrote:
>
> Jon Turney wrote:
> > On 06/03/2024 15:39, Christian Franke via Cygwin-apps wrote:
> >> Jon Turney wrote:
> >>>
> >>> Thanks!
> >>>
> >>>>
> >>>> libafflib_CONTENTS="
> >>>>     usr/bin/cygafflib-*.dll
> >>>
> >>> Any reason why this package doesn't include the soversion, i.e. why
> >>> not libafflib0?
> >>>
> >>
> >> Libtsk and libafflib are my first library packages, so I'm not sure
> >> what the policy is. My recent package libtsk has been accepted
> >> without soversion, so I omitted it also here. I assumed that the
> >> soversion will
> >
> > I'm going to suggest that was an oversight in the review.
>
> Should I also rename libtsk to libtsk19 in the planned sleutkit-*-2
> package which will add afflib support ?

yes please

> The original package is only a few days old and has possibly only a
> small but experienced audience, so I expect not much worries if the
> change will be explained in the announcement.

not worries at all if you use

libtsk19_OBSOLETES=libtsk

see
https://cygwin.github.io/cygport/pkg_pkg_cygpart.html#PKG_OBSOLETES

Regards
Marco

  reply	other threads:[~2024-03-07  5:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06 13:53 Christian Franke
2024-03-06 14:31 ` Jon Turney
2024-03-06 15:39   ` Christian Franke
2024-03-06 20:50     ` Jon Turney
2024-03-06 22:26       ` Christian Franke
2024-03-07  5:43         ` marco atzeri [this message]
2024-03-08  8:53           ` Christian Franke
2024-03-22 18:45             ` Christian Franke
2024-03-21  9:04         ` Christian Franke
2024-03-21 16:09           ` Jon Turney

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='CAB8Xom_r8Z50bvv3EOu6KDNYSV6h=hi4K78rRCpYsvhk-M9pqQ@mail.gmail.com' \
    --to=marco.atzeri@gmail.com \
    --cc=Christian.Franke@t-online.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).