From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin-apps@cygwin.com
Subject: Re: Unmaintained packages in base package set
Date: Sat, 23 Dec 2023 12:42:14 +0900 [thread overview]
Message-ID: <20231223124214.75ba63e5bed48275c3e1dfa5@nifty.ne.jp> (raw)
In-Reply-To: <b16e6c6c-c8f1-4168-a9b2-495f56a3bc3c@dronecode.org.uk>
On Wed, 20 Dec 2023 12:16:05 +0000
Jon Turney via Cygwin-apps <cygwin-apps@cygwin.com> wrote:
> I tweaked the unmaintained packages report [1] a bit so it identifies
> 'base' and 'direct or indirect base dependencies'.
>
> (But you're quite right to point out that the build requirements for a
> native Cygwin build are also important)
>
> [1] https://cygwin.com/packages/reports/unmaintained.html
I would like to take over:
libass
fontconfig
fribidi
gnutls
openjpeg
librsvg2
snappy
libssh
dbus
gtk3
orc
tdb
db
libid3tag
libmad
taglib
if no one like to do that, because the packages
I maintain use them.
I also wonder what should we do for unchanged packaegs
such as:
libbs2b
libmodplug
lame
libasyncns
avahi
musepack
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2023-12-23 3:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 0:38 [NMU] inkscape 0.92.3-2 (Test) Mark Geisert
2023-11-30 13:45 ` Jon Turney
2023-12-01 9:17 ` Mark Geisert
2023-12-03 15:33 ` Jon Turney
2023-12-03 17:50 ` Brian Inglis
2023-12-05 13:07 ` Jon Turney
2023-12-06 17:19 ` Brian Inglis
2023-12-06 17:30 ` Brian Inglis
2023-12-20 12:16 ` Unmaintained packages in base package set Jon Turney
2023-12-21 4:27 ` Marco Atzeri
2023-12-22 2:06 ` Mark Geisert
2023-12-22 16:37 ` Jon Turney
2023-12-23 3:42 ` Takashi Yano [this message]
2023-12-23 3:51 ` Marco Atzeri
2024-01-03 4:59 ` Takashi Yano
2024-01-03 7:49 ` Marco Atzeri
2024-01-07 12:54 ` Jon Turney
2024-01-07 13:35 ` Takashi Yano
2024-01-07 15:14 ` Takashi Yano
2024-01-07 15:44 ` ASSI
2024-01-26 5:03 ` Marco Atzeri
2024-01-03 15:39 ` 1dakotaxi
2023-12-11 19:21 ` [NMU] inkscape 0.92.3-2 (Test) ASSI
2023-12-14 6:57 ` Mark Geisert
2023-12-23 0:37 ` Mark Geisert
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=20231223124214.75ba63e5bed48275c3e1dfa5@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).