| 1 |
On Mon, Feb 13, 2012 at 10:50 AM, Dirkjan Ochtman <djc@g.o> wrote: |
| 2 |
> On Mon, Feb 13, 2012 at 10:33, Corentin Chary <corentin.chary@×××××.com> wrote: |
| 3 |
>> One other thing, metadata.xml already contain a remote-id tag, which |
| 4 |
>> would be very great to help euscan do its job, but a lot of package |
| 5 |
>> are lacking it: |
| 6 |
>> - Should we patch repoman to scan SRC_URI and issue a warning when it |
| 7 |
>> looks like an URI that match a well known remote-id |
| 8 |
>> - Should we write a script to update metadata.xml ? It would be easy |
| 9 |
>> for rubygem, pypi and pear packages. |
| 10 |
>> |
| 11 |
>> Any comment ? Objections ? Ideas ? |
| 12 |
> |
| 13 |
> I like the idea for keeping the data somewhere for known-insane cases, |
| 14 |
> and metadata.xml sounds like it might be fine. But I don't think we |
| 15 |
> should add anything for the likes of PyPI, if we can easily derive |
| 16 |
> that we should look on PyPI some other way (i.e. for python, many |
| 17 |
> packages list a PyPI page in their HOMEPAGE). |
| 18 |
|
| 19 |
For pypi (and some others), looking at SRC_URI is enought: it starts |
| 20 |
with mirror://pypi/. |
| 21 |
Still for those <upstream><remote-id> *must* be set because the |
| 22 |
package name is not always exactly the same as in gentoo. Currently |
| 23 |
euscan tries to guess it, but it is not always accurate. |
| 24 |
Most of the time, if remote-id is set, we don't need "version-scan" |
| 25 |
because upstream provides a stable API to list versions. |
| 26 |
|
| 27 |
|
| 28 |
-- |
| 29 |
Corentin Chary |
| 30 |
http://xf.iksaif.net |
Archives