From: Joonas Niilola <juippis@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Last-rite: app-misc/neofetch
Date: Fri, 20 Oct 2023 21:27:23 +0300 [thread overview]
Message-ID: <ce43d755-579a-4c01-8564-7288e0358cf4@gentoo.org> (raw)
In-Reply-To: <1442dfa8-82c4-4ab3-b5f2-817ddb10e822@gentoo.org>
On 20.10.2023 10.38, Joonas Niilola wrote:
> Upstream is totally abandoned with no updates for 2 years. The situation
> has spawned multiple forks and there are different maintained
> alternatives available now in Gentoo's repository. To list a few:
> fastfetch, hyfetch, screenfetch
>
> If you're aware of more/better alternatives, please add them to the
> package.mask file at your will. Bug #916040
>
> -- juippis
Hey,
so my reason for removal was that the upstream issue number is growing
weekly and there's no one fixing them. Apparently a new fork was made
where the new authors have been fixing bugs / merging PRs from neofetch
and it seemed reasonable to switch to that. But neofetch does do the job
of showing Gentoo-logo just fine I guess...
but I also want to point out it's literally a single wgettable bash
script and I personally don't see much value in keeping it, but people
seem to love it too much :) so let's keep it. And I agree, neofetch is
the original, it has a legendary status.
-- juippis
prev parent reply other threads:[~2023-10-20 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 7:38 [gentoo-dev] Last-rite: app-misc/neofetch Joonas Niilola
2023-10-20 12:30 ` Pascal Jaeger
2023-10-20 12:39 ` Joonas Niilola
2023-10-20 12:52 ` Andrew Ammerlaan
2023-10-21 8:31 ` Jonas Stein
2023-10-20 18:27 ` Joonas Niilola [this message]
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=ce43d755-579a-4c01-8564-7288e0358cf4@gentoo.org \
--to=juippis@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