From: opfer@gentoo.org (Christian Faulhammer)
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: missing metadata.xml
Date: Thu, 23 Nov 2006 11:14:01 +0100 (MET) [thread overview]
Message-ID: <A5PYRhtbeKB@v-li.fqdn.th-h.de> (raw)
In-Reply-To: <4564BC3C.1080008@gentoo.org>
Tach Steve, 0x2B859DE3 (PGP-PK-ID)
Steve Dibb schrieb:
> 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:
Nice idea, but you should really add <herd>no-herd</herd> as this is
required if there is only a "maintainer".
By the way, I tagged some metadata files with appropriate herd (where I am
allowed):
app-emacs/cperl-mode emacs
dev-lisp/cl-asdf-binary-locations common-lisp
I suggest the following changes:
app-misc/baobab vapier and/or Gnome (as this is part of Gnome
2.16)
dev-scheme/guile-pg scheme
dev-scheme/kawa scheme
dev-scheme/mzscheme scheme
dev-util/cweb text-markup and/or lang-misc
V-Li
--
Fingerprint: 68C5 D381 B69A A777 6A91 E999 350A AD7C 2B85 9DE3
http://www.gnupg.org/
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-11-23 11:24 UTC|newest]
Thread overview: 18+ 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
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 ` Christian Faulhammer [this message]
2006-11-24 4:39 ` [gentoo-dev] " 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
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=A5PYRhtbeKB@v-li.fqdn.th-h.de \
--to=opfer@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