Re: [gentoo-dev] GLEP 46: Allow upstream tags in metadata.xml

[Rob Cakebread]

Santiago M. Mola wrote:
>
> The GLEP should be updated. "Motivation" section does not seem to
> justify the changes. IMO Meatoo [1]  (and its hipothetical rewrite
> using Doapspace [2]) would be the right tool to detect version bumps.
> Maybe metadata.xml should contain a  Freshmeat or DOAP entry so meatoo
> could get more automation.
>
> Anyway, I don't know how much would take the new version of meatoo.
> Pythonhead, could you give us some news about it? Or it's just planned
> for the long-term future?
>
>
> [1] http://meatoo.gentooexperimental.org/
> [2] http://blog.doapspace.org/
>


Sorry, I missed this email, but I'll be at the council meeting to listen 
in on talk about GLEP 46.

Having Freshmeat, SourceForge etc. project id's in metadata.xml sounds 
great.

I would gladly write a tool to go through SourceForge and Freshmeat's 
metadata and match project names to ebuild package names using HOMEPAGE. 
  I already have code to parse FLOSSMole's[1] metadata, so it'd be 
simple to whip up quickly.

doapspace.org has an API that lets you give a SourceForge, Freshmeat, 
PyPI and RubyForge project name and get metadata back, so having a link 
to the DOAP's URL in metadata.xml isn't really needed for those. For 
self-hosted projects, we could either put a link to the DOAP in 
metadata.xml, or simply make sure the HOMEPAGE matches the homepage in 
the DOAP itself. The second is preferable because the URL to the DOAP 
could change.

Meatoo will be much more accurate after I cross-reference metadata from 
FLOSSMole to map Gentoo package names to other forge/package index 
names. Once that's done, we'll have very accurate version bump info that 
can be looked up by herd/maintainer, from SourceForge, RubyForge, 
Freshmeat etc.

Rob

[1] http://ossmole.sourceforge.net

-- 
gentoo-dev@l.g.o mailing list