From: Johannes Weiner <hnaz@tutorialzone.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Pinboard of outdated ports
Date: Tue, 24 May 2005 07:26:49 +0200 [thread overview]
Message-ID: <20050524052649.GA5733@neurogen> (raw)
In-Reply-To: <429262B1.90109@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]
> What it seems like you're doing here is saying more work for the
> developers is fine, if it makes things easier for the users. (Developers
> will just cvs up, which is likely faster than dealing with a web interface.)
I dunno if it's really big work to have a look at one site to see if
there are ebuilds you missed when they were updated.
It was not my intention to make really more work. It was just to find a faster
way for outdated ebuilds getting updated.
> Although that may be nice in concept, in reality developers may have
> quite limited time. Most things that detract from the time they spend on
> development rather than on searching around and figuring out what to do
> makes Gentoo worse. It has yet to be proven that your suggestion would
> take more time, but that's the feeling I have.
>
> If one knows how to search bugzilla and understands how maintainers are
> indicated, this can be comparably easy already. Something like this
> could give you a search:
>
> 1. Use herdstat to find the maintainer, if you aren't comfortable with
> the metadata.xml files.
>
> $ herdstat --metadata xorg-x11
> Package: x11-base/xorg-x11
> Herds(1): x11
> Maintainers(0): none
> Homepage: http://xorg.freedesktop.org/
> Description: X11 implementation by X.Org Foundation
Will try this, my idea seems to be refused anyway.
--
Today is Prickle-Prickle, the 71st day of Discord in the YOLD 3171
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-24 5:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 17:11 [gentoo-dev] Pinboard of outdated ports Johannes Weiner
2005-05-23 19:46 ` Tom Martin
2005-05-23 22:47 ` Johannes Weiner
2005-05-24 14:47 ` Tom Martin
2005-05-24 15:24 ` Diego 'Flameeyes' Pettenò
2005-05-24 16:16 ` Rob Cakebread
2005-05-24 21:50 ` Johannes Weiner
2005-05-23 19:50 ` Donnie Berkholz
2005-05-23 22:50 ` Johannes Weiner
2005-05-23 23:09 ` Donnie Berkholz
2005-05-24 5:26 ` Johannes Weiner [this message]
2005-05-24 13:01 ` David Stanek
2005-05-24 13:36 ` Chris Gianelloni
2005-05-24 20:44 ` [gentoo-dev] " R Hill
2005-05-24 21:01 ` Diego 'Flameeyes' Pettenò
2005-05-24 21:12 ` Donnie Berkholz
2005-05-24 21:23 ` Diego 'Flameeyes' Pettenò
2005-05-25 13:36 ` Chris Gianelloni
2005-05-24 23:03 ` Homer Parker
2005-05-25 13:29 ` Chris Gianelloni
2005-05-26 0:09 ` R Hill
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=20050524052649.GA5733@neurogen \
--to=hnaz@tutorialzone.de \
--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