Re: [DEPRECATED] perl distributions

[Achim Gratz via Cygwin-apps]

Jon Turney via Cygwin-apps writes:
> 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...)

When I wrote this originally, there was still the possibility that
someone could reasonably keep the previous Perl version around and then
expect to still have these packages available.  That was my reason for
not wanting to just delete them at that time, anyway.


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

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

Re: [DEPRECATED] perl distributions

[Jon Turney via Cygwin-apps]

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-GConfAchim Gratz
perl-Gnome2-Rsvg Achim Gratz
perl-Gnome2-VFS  Achim Gratz
perl-Gnome2-Vte  Achim Gratz
perl-Gnome2-Wnck Achim Gratz
perl-Gtk2Achim Gratz
perl-Gtk2-GladeXML   Achim Gratz
perl-Gtk2-Notify Achim Gratz
perl-Gtk2-SourceView2Achim 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...)