From: "Kevin F. Quinn" <kevquinn@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Re: packages going into the tree with non-gentoo maintainers
Date: Sun, 3 Sep 2006 20:46:16 +0200 [thread overview]
Message-ID: <20060903204616.2a25695d@c1358217.kevquinn.com> (raw)
In-Reply-To: <edeogp$qui$1@sea.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1318 bytes --]
On Sun, 03 Sep 2006 16:22:37 +0200
Stefan Schweizer <genstef@gentoo.org> wrote:
> Paul de Vrieze wrote:
> > For this stuff, add a comment to the metadata.xml file. Don't do it
> > in this less than obvious way.
>
> arch teams for example will still contact me then for stabilizing, I
> do not want that. jeeves and herdstat do not support comments and the
> metadata is not often read directly.
If you don't care whether a package is stable or not, just let the arch
team go ahead and do what they need to do to stabilise when they wish
to. The role of package maintainer has nothing to do with
stabilisation, which is the preserve of the arch teams.
> > The maintainer must still be someone with a
> > gentoo email.
>
> is that written down somewhere? I was under the impression that it is
> allowed and have seen it used for example
> in /usr/portage/www-client/links/metadata.xml
You'll notice that there are two maintainer blocks in there, one for
the non-gentoo "third-party" maintainer, and one for the Gentoo dev who
proxies - the "official Gentoo" maintainer. There are several packages
like this.
What I'm conerned about is packages that have no Gentoo maintainer,
something that should obviously never happen for packages in the
official tree.
--
Kevin F. Quinn
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-09-03 18:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-03 9:20 [gentoo-dev] packages going into the tree with non-gentoo maintainers Kevin F. Quinn
2006-09-03 10:12 ` Carsten Lohrke
2006-09-03 11:57 ` [gentoo-dev] " Stefan Schweizer
2006-09-03 12:51 ` Bryan Ãstergaard
2006-09-03 14:36 ` [gentoo-dev] " Stefan Schweizer
2006-09-06 23:35 ` Andrej Kacian
2006-09-07 2:09 ` Carsten Lohrke
2006-09-07 2:37 ` Stephen P. Becker
2006-09-07 3:10 ` Brian Harring
2006-09-07 11:29 ` Stephen P. Becker
2006-09-07 11:48 ` Jakub Moc
2006-09-07 13:25 ` Carsten Lohrke
2006-09-07 14:42 ` Simon Stelling
2006-09-07 14:51 ` Jakub Moc
2006-09-07 15:07 ` Simon Stelling
2006-09-07 15:22 ` Carsten Lohrke
2006-09-07 15:16 ` Kevin F. Quinn
[not found] ` <200609071726.54054.carlo@gentoo.org>
2006-09-07 15:37 ` Jakub Moc
2006-09-07 3:13 ` Alec Warner
2006-09-07 11:09 ` Simon Stelling
2006-09-07 3:22 ` Luca Barbato
2006-09-07 5:58 ` [gentoo-dev] " Stefan Schweizer
2006-09-07 11:08 ` Carsten Lohrke
2006-09-07 9:11 ` [gentoo-dev] " Stuart Herbert
2006-09-07 10:17 ` Danny van Dyk
2006-09-07 10:21 ` Jon Portnoy
2006-09-07 11:05 ` Carsten Lohrke
2006-09-07 11:25 ` Diego 'Flameeyes' Pettenò
2006-09-07 13:26 ` Carsten Lohrke
2006-09-03 13:20 ` [gentoo-dev] " Kevin F. Quinn
2006-09-03 14:11 ` [gentoo-dev] " Stefan Schweizer
2006-09-03 13:55 ` [gentoo-dev] " Paul de Vrieze
2006-09-03 14:22 ` [gentoo-dev] " Stefan Schweizer
2006-09-03 18:46 ` Kevin F. Quinn [this message]
2006-09-03 23:54 ` [gentoo-dev] " Ryan Hill
2006-09-04 7:20 ` Kevin F. Quinn
2006-09-07 3:10 ` [gentoo-dev] " Mike Frysinger
2006-09-07 3:02 ` [gentoo-dev] " Mike Frysinger
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=20060903204616.2a25695d@c1358217.kevquinn.com \
--to=kevquinn@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