public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Corentin Chary <corentin.chary@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] RFC: upstream/watch in metadata.xml
Date: Mon, 13 Feb 2012 10:33:11 +0100	[thread overview]
Message-ID: <CAHR064gX-Au8mDAWNmGOw5RZadn-zdfBs-Y9_5-dcodLKHs5TQ@mail.gmail.com> (raw)

As some may know, I'm working on euscan, and currently euscan only use
CPV and SRC_URI to find new upstream versions.
This works well if upstream url and version scheme is sane or if
upstream has an API for that (rubygem, pypi, pecl, pear), but it's far
from optimal.

Debian use a specific file for that: debian/watch and it looks like
that (for media-plugins/vdr-softdevice):

opts=downloadurlmangle=s/prdownload/download/ \
   http://developer.berlios.de/project/showfiles.php?group_id=2051 \
   http://prdownload.berlios.de/softdevice/vdr-softdevice-(.+).tgz

opts specify some options to mangle the final url, and then there is a
list of url to scan. man uscan for more informations.

Currently, if you run euscan on this package, it doesn't work at all:
http://euscan.iksaif.net/package/media-plugins/vdr-softdevice/
1/ it's hosted on gentoo mirrors, and scanning them takes too long
because all files are in the same directory
2/ the url doesn't contain the version

So, to help euscan (and other tools) for some package, I think we
could introduce some hints in metadata.xml. This would extend the
existing "upstream" element:

<upstream>
<version-scan downloadurlmangle="s/prdownload/download/">http://developer.berlios.de/project/showfiles.php?group_id=2051
\
   http://prdownload.berlios.de/softdevice/vdr-softdevice-(.+).tgz</version-scan>
</upstream>

The format is not defined yet, but it would probably look like
debian/watch, that would allow to write a script to import (valid)
debian/watch files into associated metadata.xml when needed.

One other thing, metadata.xml already contain a remote-id tag, which
would be very great to help euscan do its job, but a lot of package
are lacking it:
- Should we patch repoman to scan SRC_URI and issue a warning when it
looks like an URI that match a well known remote-id
- Should we write a script to update metadata.xml ? It would be easy
for rubygem, pypi and pear packages.

Any comment ? Objections ? Ideas ?

Thanks,

-- 
Corentin Chary
http://xf.iksaif.net



             reply	other threads:[~2012-02-13  9:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13  9:33 Corentin Chary [this message]
2012-02-13  9:50 ` [gentoo-dev] RFC: upstream/watch in metadata.xml Dirkjan Ochtman
2012-02-13  9:57   ` Corentin Chary
2012-02-13  9:52 ` Robin H. Johnson
2012-02-13  9:59   ` Corentin Chary
2012-02-13  9:59     ` Corentin Chary

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=CAHR064gX-Au8mDAWNmGOw5RZadn-zdfBs-Y9_5-dcodLKHs5TQ@mail.gmail.com \
    --to=corentin.chary@gmail.com \
    --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