From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: cygwin-pkg-maint cleanup
Date: Tue, 29 Nov 2022 21:36:49 +0000 [thread overview]
Message-ID: <305bd194-d57c-4eeb-5eca-531c114c8e50@dronecode.org.uk> (raw)
In-Reply-To: <da77ae73-afa5-1277-c8e2-7e3246908d6c@dronecode.org.uk>
I've done another clean-up of cygwin-pkg-maint, removing those source
packages names which no longer exist after x86 was archived (i.e only
existed as x86 packages)
> cygwin64-* ORPHANED (Yaakov Selkowitz) 32-bit only by design
> db4.8 OBSOLETE (Dr. Volker Zell) Obsoletion by db 5.x was done in an unusual way
> gnome-characters ORPHANED (Yaakov Selkowitz) Presumably build problems on x64. Whole GNOME stack needs looking at
> hdparm ORPHANED (Christian Franke) Presumably build problems on x64. Cygwin-specific port of hdparm
> sushi ORPHANED (Yaakov Selkowitz) Presumably build problems on x64. GNOME file manager previewer. Whole GNOME stack needs looking at
> xemacs ORPHANED (Dr. Volker Zell) Is it dead yet?
> xemacs-mule-sumo ORPHANED (Dr. Volker Zell) ditto
> xemacs-sumo ORPHANED (Dr. Volker Zell) ditto
> xview Jon Turney 32-bit only by design
Note that a lot of long obsolete install package names have also
disappeared (e.g. ash, which was obsoleted by dash in 2009, etc.)
next prev parent reply other threads:[~2022-11-29 21:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 12:57 Jon Turney
2022-06-25 17:24 ` Marco Atzeri
2022-11-29 21:36 ` Jon Turney [this message]
2022-11-30 21:34 ` Ken Brown
2022-12-02 15:06 ` Jon Turney
2022-12-01 4:55 ` Yaakov Selkowitz
2022-12-02 15:06 ` 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=305bd194-d57c-4eeb-5eca-531c114c8e50@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).