On 26-12-2005 22:11:46 -0200, Marcelo Ges wrote: > Fellow Gentooers, > > Here is a draft of an enhancement proposal that should allow upstream > information to be included in metadata.xml: > > http://dev.gentoo.org/~vanquirius/glep-0099.txt
using http://www.gentoo.org/proj/en/glep/glep-0046.html 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 written as "mailto:[EMAIL PROTECTED]"? Using an URI gives a nice specified format (already including the http(s) which you require) and should go with regular URI parsers. 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 the 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. Not clear from the text, but I take it from the example that remote-id has an attribute named "type" which points to some source. Is there a reason to make that an attribute, instead of a tag? Also, the remote-id tag in the example has a TEXT node which apparently is the id, but needs some information in order to track it. Taking your SourceForge example: <remote-id type="sourceforge">adium</remote-id> Usually for SourceForge means that "adium" in this case is the "UNIX project name", hence an URL such as http://sourceforge.net/projects/adium points to the project's SourceForge home, while http://adium.sourceforge.net/ points to the project's home page. It's not clear for me where this is different from the home page URL in the ebuild itself. I don't know if FreshMeat can be a real project home. 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 to use an id, and not for instance an URI to the remote 'developers' homepage/resource? Observation: the added data is mainly targetted at developers, not users. Given the ongoing discussion, this might be an interesting side note. In an overlay I'm currently keeping 'portnotes' in metadata.xml, which basically give us developers a quick look on what was necessary to port an ebuild. This is by no means interesting for a regular user, and we put it in metadata.xml because that allows to group the portnotes, since XML is a bit more structured than a changelog. For the sake of rsyncs/speed/storage/whatever, perhaps this purely targetted at developers information should be put in a separate file, which is by default excluded in the rsync? -- gentoo-dev@gentoo.org mailing list
