public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Ammerlaan <andrewammerlaan@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last-rite: app-misc/neofetch
Date: Fri, 20 Oct 2023 14:52:47 +0200	[thread overview]
Message-ID: <78e19898-638e-4d46-8e5f-5c5568d4b7da@gentoo.org> (raw)
In-Reply-To: <027c9c69-2aef-4dc7-8456-f6241643d338@gentoo.org>

On 20/10/2023 14:39, Joonas Niilola wrote:
> On 20.10.2023 15.30, Pascal Jaeger wrote:
>>
>> This is only two years without a release. We have packages way way older
>> than that.
>> I know fetch scripts have a reputation, but this thing is kind
>> of a staple in the community and it is still widely used.
>>
>> I can jump in as a proxy maintainer if that is the problem.
>>
>> Pascal
>>
> 
> Hey,
> 
> I was looking at these metrics:
> https://github.com/dylanaraps/neofetch/branches/active
> https://github.com/dylanaraps/neofetch/branches
> https://github.com/dylanaraps/neofetch/issues
> https://github.com/dylanaraps/neofetch/pulls
> 
> and it's not looking good. Do we have the wrong upstream in our current
> ebuild?
> https://packages.gentoo.org/packages/app-misc/neofetch

Other distro's seem to have the same upstream, so I guess it is correct: 
https://repology.org/project/neofetch/information

Best regards,
Andrew


  reply	other threads:[~2023-10-20 12:52 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 [this message]
2023-10-21  8:31     ` Jonas Stein
2023-10-20 18:27 ` [gentoo-dev] " Joonas Niilola

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=78e19898-638e-4d46-8e5f-5c5568d4b7da@gentoo.org \
    --to=andrewammerlaan@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