| 1 |
On 26-12-2005 22:11:46 -0200, Marcelo Ges wrote: |
| 2 |
> Fellow Gentooers, |
| 3 |
> |
| 4 |
> Here is a draft of an enhancement proposal that should allow upstream |
| 5 |
> information to be included in metadata.xml: |
| 6 |
> |
| 7 |
> http://dev.gentoo.org/~vanquirius/glep-0099.txt |
| 8 |
|
| 9 |
using http://www.gentoo.org/proj/en/glep/glep-0046.html |
| 10 |
|
| 11 |
The bugs-to tag can hold either an email address or URL. Not a big |
| 12 |
issue, but why not make it an URI, such that an email address is written |
| 13 |
as "mailto:foo@×××.bar"? Using an URI gives a nice specified format |
| 14 |
(already including the http(s) which you require) and should go with |
| 15 |
regular URI parsers. |
| 16 |
|
| 17 |
Given the URI thing, maybe it can be useful to define the changelog tag |
| 18 |
to have an URI as well, since some upstreams ship the changelog with the |
| 19 |
sources and don't put them on the web. In such case you might want to |
| 20 |
use a "file://" URI to point to the file on disk when installed? I |
| 21 |
realise this is tricky. |
| 22 |
|
| 23 |
Not clear from the text, but I take it from the example that remote-id |
| 24 |
has an attribute named "type" which points to some source. Is there a |
| 25 |
reason to make that an attribute, instead of a tag? Also, the remote-id |
| 26 |
tag in the example has a TEXT node which apparently is the id, but needs |
| 27 |
some information in order to track it. Taking your SourceForge example: |
| 28 |
<remote-id type="sourceforge">adium</remote-id> |
| 29 |
Usually for SourceForge means that "adium" in this case is the "UNIX |
| 30 |
project name", hence an URL such as |
| 31 |
http://sourceforge.net/projects/adium |
| 32 |
points to the project's SourceForge home, while |
| 33 |
http://adium.sourceforge.net/ |
| 34 |
points to the project's home page. It's not clear for me where this is |
| 35 |
different from the home page URL in the ebuild itself. I don't know if |
| 36 |
FreshMeat can be a real project home. What I wanted to say, where is |
| 37 |
the logic stored on how to make this id into some resource? And if you |
| 38 |
store that logic somewhere, why not in the XML structure? Any reason to |
| 39 |
use an id, and not for instance an URI to the remote 'developers' |
| 40 |
homepage/resource? |
| 41 |
|
| 42 |
Observation: the added data is mainly targetted at developers, not |
| 43 |
users. Given the ongoing discussion, this might be an interesting side |
| 44 |
note. In an overlay I'm currently keeping 'portnotes' in metadata.xml, |
| 45 |
which basically give us developers a quick look on what was necessary to |
| 46 |
port an ebuild. This is by no means interesting for a regular user, and |
| 47 |
we put it in metadata.xml because that allows to group the portnotes, |
| 48 |
since XML is a bit more structured than a changelog. For the sake of |
| 49 |
rsyncs/speed/storage/whatever, perhaps this purely targetted at |
| 50 |
developers information should be put in a separate file, which is by |
| 51 |
default excluded in the rsync? |
| 52 |
-- |
| 53 |
gentoo-dev@g.o mailing list |
Archives