From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin-apps@cygwin.com
Subject: Re: Unmaintained packages in base package set
Date: Wed, 3 Jan 2024 13:59:32 +0900 [thread overview]
Message-ID: <20240103135932.cbdc2a81a832faf1bfd60f86@nifty.ne.jp> (raw)
In-Reply-To: <6f0dfdd5-d41b-41de-b522-411cd728da8c@gmail.com>
On Sat, 23 Dec 2023 04:51:22 +0100
Marco Atzeri wrote:
> On 23/12/2023 04:42, Takashi Yano via Cygwin-apps wrote:
> > 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.
>
> all in one shot ?
> I suggest to start with the smaller beasts one by one or small groups
> I suspect GTK3 needs a lot of effort
Thanks for the advice.
Now, GTK3 package of 3.24.39 has been successfully built and packaged
in my environment with updating some other related packages.
So, firstly, I would like to take over following packages that are related
to GTK3.
fribidi 0.19.7 -> 1.0.13
libdatrie 0.28 -> 0.2.13
libthai 0.1.26 -> 0.1.29
pango1.0 1.40.14 -> 1.51.0
atk1.0 2.26.1 -> 2.38.0
gtk3 3.22.28 -> 3.24.39
> > libass
> > fontconfig
> > gnutls
> > openjpeg
> > snappy
> > libssh
> > dbus
> > orc
> > tdb
> > db
> > libid3tag
> > libmad
> > taglib
will be next steps. I will try them one by one.
> I could be interested in librsvg2 for the same reason of you
Please feel free to take it over. I'd withdraw from librsvg2.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2024-01-03 4:59 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
2023-12-23 3:51 ` Marco Atzeri
2024-01-03 4:59 ` Takashi Yano [this message]
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=20240103135932.cbdc2a81a832faf1bfd60f86@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).