public inbox for
 help / color / mirror / Atom feed
From: Achim Gratz <>
Subject: Re: calm/mksetupini changes
Date: Mon, 23 May 2022 20:12:19 +0200	[thread overview]
Message-ID: <87leusjeyk.fsf@Rainer.invalid> (raw)
In-Reply-To: <> (Lemures Lemniscati's message of "Mon, 23 May 2022 22:09:50 +0900")

Lemures Lemniscati writes:
> Although libiconv2 is contained in the list above,
> I don't think it is deprecated.

I think you missed the point that Jon was trying to make: we currently
have many library packages at various versions (those with the actual
libraries) that other packages depended on at some point in time.  If
there already is a newer version of such a package and there are still
dpendencies that point to an older version, that means those packages
should eventually get rebuilt to use that newer version (if not ABI
compatible) or just use the newest version without any prodding (if ABI
compatible), which in turn means that the old versions can get removed
along with the corresponding source and debuginfo packages that were
solely kept alive by these dependencies.

In the case of libiconv2 the current version for Cygwin is 1.17-1 and
the library should be ABI compatible with all previous versions, so
these old versions up to and including 1.16-2 are deprecated since setup
will never install them unless forced manually.

+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:

  reply	other threads:[~2022-05-23 18:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-28 19:26 Jon Turney
2021-06-26 13:29 ` Jon Turney
2022-05-21 20:31   ` Jon Turney
2022-05-23 13:09     ` Lemures Lemniscati
2022-05-23 18:12       ` Achim Gratz [this message]
2022-05-23 18:44         ` Achim Gratz
2022-05-24  9:50           ` Lemures Lemniscati
2022-05-23 18:37       ` Jon Turney
2022-05-24 10:05         ` Lemures Lemniscati
2022-05-24 12:57           ` Jon Turney
2022-05-26  8:55             ` Lemures Lemniscati

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87leusjeyk.fsf@Rainer.invalid \ \ \

* 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).