From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org)
by nuthatch.gentoo.org with esmtp (Exim 4.54)
id 1ErHoy-0006dW-Dk
for garchives@archives.gentoo.org; Tue, 27 Dec 2005 16:37:08 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jBRGYlEl000787;
Tue, 27 Dec 2005 16:34:47 GMT
Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207])
by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jBRGWhqM029455
for <gentoo-dev@lists.gentoo.org>; Tue, 27 Dec 2005 16:32:44 GMT
Received: by wproxy.gmail.com with SMTP id i23so405915wra
for <gentoo-dev@lists.gentoo.org>; Tue, 27 Dec 2005 08:34:15 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=beta; d=gmail.com;
h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
b=ANQryymsuxRB1Q4FAGBN9rrPQOEOp9lsqPrygNAdwsczVCWBIgX8bfR1+1ipp6Q9MsOwOf702TzNGcwIGCk0qYOCJTC5Os4fwsf+59WuYSR7Fo9wxSN1wuQTSx0Ib2JcveiPW4aQReuroBVHsvAgR3fHDF2KUIf1ssWAKUDPrIg=
Received: by 10.54.112.1 with SMTP id k1mr7370221wrc;
Tue, 27 Dec 2005 08:34:15 -0800 (PST)
Received: by 10.54.122.8 with HTTP; Tue, 27 Dec 2005 08:34:14 -0800 (PST)
Message-ID: <9e83288a0512270834r66334d2dvfae2e8160d27dee1@mail.gmail.com>
Date: Tue, 27 Dec 2005 14:34:14 -0200
From: =?ISO-8859-1?Q?Marcelo_G=F3es?= <vanquirius@gentoo.org>
Sender: marcelogoes@gmail.com
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Allow upstream tags in metadata.xml
In-Reply-To: <200512262350.38124.electronerd@electronerdia.net>
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
References: <9e83288a0512261611v6861e351tb75367c7a30e264e@mail.gmail.com>
<200512262350.38124.electronerd@electronerdia.net>
X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id jBRGWhqM029455
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by robin.gentoo.org id jBRGYlGO000787
X-Archives-Salt: 3da2f808-35c3-45bc-a4f1-c2b6d0e2a743
X-Archives-Hash: 9bcc6b1a54e817f666693cb98239fc88
On 12/27/05, John Myers <electronerd@electronerdia.net> wrote:
> What if upstream is more than one person, but less than an organization=
? What
> if there is more than one upstream such as for gentoo-sources, where th=
e
> maintainer of each of the patchsets could be considered an upstream?
I don't see a problem with having multiple "name" and "email" fields.
Perhaps there could be an additional "description" tag to discriminate
what each person is responsible for.
> if this is to be subject to automated processing, shouldn't there be a
> registry of valid "type" values maintaining a definition of what the va=
lue of
> the element corresponds to for each type?
Yes. Thus far, I have in mind freshmeat, sourceforge and cpan, but
other types can be added later.
On 12/27/05, Grobian <grobian@gentoo.org> wrote:
> The bugs-to tag can hold either an email address or URL. Not a big
> issue, but why not make it an URI, such that an email address is writte=
n
> as "mailto:foo@bar.bar"? Using an URI gives a nice specified format
> (already including the http(s) which you require) and should go with
> regular URI parsers.
Sounds good enough.
> Given the URI thing, maybe it can be useful to define the changelog tag
> to have an URI as well, since some upstreams ship the changelog with th=
e
> sources and don't put them on the web. In such case you might want to
> use a "file://" URI to point to the file on disk when installed? I
> realise this is tricky.
Hmmm... I'm not sure about this one. Not only is it tricky, but the
whole point of this GLEP is to facilitate the finding of online
up-to-date information. If there is no online changelog, I think it
may be better just to ommit this field.
> What I wanted to say, where is
> the logic stored on how to make this id into some resource? And if you
> store that logic somewhere, why not in the XML structure? Any reason t=
o
> use an id, and not for instance an URI to the remote 'developers'
> homepage/resource?
Yes, there is a logic. I think it is easier to maintain an external
list, such as we do with "thirdpartymirrors". The point of listing
alternative resources is that they may include features not provided
by upstream itself. For example, an announce list that lets one know
when a new version has been released.
On 12/27/05, Paul de Vrieze <pauldv@gentoo.org> wrote:
> What is the reason for having an upstream tag?
Aggregate useful upstream information in one place.
> Wouldn't it be easier to just name the tags properly.
How?
> And what about just using a general attribute tag
> like <meta name=3D"upstreammaint" value=3D"foo@bar.com"/>
It's not bad, but isn't it better to have it in the structured way we
suggest? It's graphically easier to read/write.
Cheers! I'll be back the first week of January :-).
Marcelo
--
Marcelo G=F3es
marcelogoes@gmail.com
vanquirius@gentoo.org
--=20
gentoo-dev@gentoo.org mailing list