From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
Achim Gratz <Stromeko@nexgo.de>
Subject: Re: [DEPRECATED] perl distributions
Date: Fri, 6 Jan 2023 13:46:50 +0000 [thread overview]
Message-ID: <d87126c5-375c-0c49-f2fa-9cc9e28d0a98@dronecode.org.uk> (raw)
In-Reply-To: <87sg6i3ieg.fsf@Rainer.invalid>
On 30/01/2021 09:04, Achim Gratz wrote:
>
> The following distributions will no longer be available after the
> perl-5.32 release as they have been deprecated upstream:
>
> perl-Gnome2 Achim Gratz
> perl-Gnome2-Canvas Achim Gratz
> perl-Gnome2-GConf Achim Gratz
> perl-Gnome2-Rsvg Achim Gratz
> perl-Gnome2-VFS Achim Gratz
> perl-Gnome2-Vte Achim Gratz
> perl-Gnome2-Wnck Achim Gratz
> perl-Gtk2 Achim Gratz
> perl-Gtk2-GladeXML Achim Gratz
> perl-Gtk2-Notify Achim Gratz
> perl-Gtk2-SourceView2 Achim Gratz
> perl-Gtk2-Spell Achim Gratz
> perl-Gtk2-Unique Achim Gratz
> perl-Gtk2-WebKit Achim Gratz
>
> There are no external dependencies to these, so please just mark them as
> OBSOLETE.
I've vaulted all versions of these packages. Sorry for taking so long to
get around to this.
At the moment, 'OBSOLETE' in cygwin-pkg-maint has a very specific
meaning: the line is simply ignored by calm.
If you just mark a package as OBSOLETE without any other action, calm's
going to warn about an unexpected package in the relarea.
That works in the case when a package has been replaced by something
else, and the historically necessary rearrangement to make the obsoleted
package a sub-package of the package which replaces it has happened. (we
didn't just remove the obsolete package because historically the
obsoletion was recorded in the obsoleted package's metadata).
(There's a whole other set of considerations for packages with the
category '_obsolete', but again I think those are historical artefacts)
I'm not sure what the word is for the status of these packages (but they
are all deprecated upstream, don't have a direct replacement, probably
aren't of any use to anybody, so clearly keeping them around any longer
is pointless...)
next prev parent reply other threads:[~2023-01-06 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 9:04 Achim Gratz
2021-01-30 15:21 ` Marco Atzeri
2021-01-31 17:15 ` Achim Gratz
2021-02-11 17:08 ` Jon Turney
2022-07-09 7:00 ` Marco Atzeri
2022-07-09 12:05 ` Jon Turney
2023-01-06 13:46 ` Jon Turney [this message]
2023-01-06 19:36 ` Achim Gratz
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=d87126c5-375c-0c49-f2fa-9cc9e28d0a98@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=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).