From: "Bryan Østergaard" <kloeri@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] missing metadata.xml
Date: Thu, 23 Nov 2006 00:29:34 +0100 [thread overview]
Message-ID: <20061122232934.GS12483@woodpecker.gentoo.org> (raw)
In-Reply-To: <4564BC3C.1080008@gentoo.org>
On Wed, Nov 22, 2006 at 02:08:12PM -0700, Steve Dibb wrote:
> Hi guys,
>
> There are more than a few packages with missing metadata.xml in the
> portage tree. I've setup my funky little QA website to report on which
> ones fall in that category, and here is the list right here:
>
> http://spaceparanoids.org/gentoo/gpnl/qa.php?q=metadata
>
> I've spent the morning fixing up most of them, adding blank metadata.xml
> to them and assigning maintainer-needed@gentoo.org as the main
> maintainer, which in hindsight was probably not the best approach (my
> apologies).
>
> Anyway, either way, it would be nice to get the few remaining packages
> cleaned up, and if one of your packages is on that list, please update
> or create the metadata.
>
> I'll still be going through the rest of them and sorting out which ones
> were last maintained by a dev that is now retired and continue assigning
> them to maintainer-needed.
>
I think the most important thing about adding "empty" metadata.xml files
with maintainer-needed as maintainer is that it _changes_ the package to
be unmaintained by definition (that's what maintainer-needed means after
all) and that we can't be sure that's actually true unless we spend a
lot of time examining each package and asking potential maintainers
if it's unmaintained.
So while I enjoy getting metadata cleaned up etc. I think it's important
to think about exactly what we're doing before "fixing" up a lot of
packages - in this case 300+ packages. You (all devs!) might even want
to ask on -dev ML if it's a good idea before touching up a huge number
of packages to make sure you don't change things in subtle,
unintentional ways.
Anyway, I appreciate you spending time on cleaning up the metadata.xml
files even if it might not have been the best idea in hindsight.
Regards,
Bryan Østergaard
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-11-22 23:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 21:08 [gentoo-dev] missing metadata.xml Steve Dibb
2006-11-22 23:29 ` Bryan Østergaard [this message]
2006-11-23 10:20 ` Jakub Moc
2006-11-23 12:40 ` Bryan Østergaard
2006-11-24 0:00 ` Andrej Kacian
2006-11-24 9:59 ` Jakub Moc
2006-11-25 0:39 ` Jeroen Roovers
2006-11-25 0:55 ` Elfyn McBratney
2006-11-24 9:47 ` Paul de Vrieze
2006-11-23 10:56 ` David Shakaryan
2006-11-23 12:37 ` Bryan Østergaard
2006-11-23 10:14 ` [gentoo-dev] " Christian Faulhammer
2006-11-24 4:39 ` Donnie Berkholz
2006-11-24 6:37 ` David Shakaryan
2006-11-24 8:13 ` Christian Faulhammer
2006-12-09 15:51 ` Ryan Hill
2006-11-24 8:11 ` Mart Raudsepp
2006-11-26 19:04 ` Christian Faulhammer
-- strict thread matches above, loose matches on Subject: below --
2007-05-10 15:19 [gentoo-dev] " Thilo Bangert
2007-05-11 22:45 ` Thilo Bangert
2007-05-13 13:18 ` Anant Narayanan
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=20061122232934.GS12483@woodpecker.gentoo.org \
--to=kloeri@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