From: Georgy Yakovlev <gyakovlev@gentoo.org>
To: gentoo-dev@lists.gentoo.org, gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev-announce] Packages up for grabs: dev-lang/typescript, gnome-extra/gnome-shell-extension-pop-shell
Date: Wed, 21 Sep 2022 22:02:23 -0700 [thread overview]
Message-ID: <20220922050223.bysldnfp222x4kf7@hydra> (raw)
Hi,
Following package up for grabs:
gnome-extra/gnome-shell-extension-pop-shell
dev-lang/typescript
I no longer uses pop-shell and it's > 1y outdated.
typescript is a build dependency and pop-shell is it's only revdep.
However, there are plenty of typescript users and package is popular.
Yes, it's npm package, but it's unique because it has no external deps.
Easy to maintain too, no bugs open, only dependency is nodejs[npm]
May use eapi8 bump.
As for pop-shell, bump will require packaging 2 extra deps:
pop-launcher
pop-shortcuts
Both are rust, the latter uses justfile instead of makefile.
It also uses rustls with ring crate, which is not portable and had no
commits since april 2022.
So my recommendation is to drop pop-shell or move to guru.
And keep typescript in repo, it's popular.
Thanks for reading!
--
Best regards,
Georgy
reply other threads:[~2022-09-22 5:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220922050223.bysldnfp222x4kf7@hydra \
--to=gyakovlev@gentoo.org \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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