1 |
Am Donnerstag, den 04.02.2010, 22:37 +0100 schrieb Tiziano Müller: |
2 |
> While some people already discovered the upstream metadata tags, there |
3 |
> are only 8 ebuilds using them so far. Mostly I am to blame for that, |
4 |
> since I forgot to send out a proper announcement. While all the required |
5 |
> information can be found in the Developer Handbook [1], here is a short |
6 |
> summary: |
7 |
> |
8 |
> The upstream tags are meant as a way to track information about |
9 |
> upstream, like: |
10 |
> - the upstream status (can make treecleaners lives easier) |
11 |
> - online documentation links (a shortcut for the user) |
12 |
> - not-so-obvious contact/bug-reporting information |
13 |
> - id of a hosting or indexing site (automated version bump checks) |
14 |
> - their alignment (mostly chaotic-neutral ;-) |
15 |
> |
16 |
> An example (copied from GLEP 46 [2] itself): |
17 |
> <upstream> |
18 |
> <maintainer status="inactive"> |
19 |
> <name>Foo Bar</name> |
20 |
> <email>foo@×××.bar</email> |
21 |
> </maintainer> |
22 |
> <maintainer status="active"> |
23 |
> <name>Foo Gentoo</name> |
24 |
> <email>foo@g.o</email> |
25 |
> </maintainer> |
26 |
> <changelog>http://foo.bar/changelog.txt</changelog> |
27 |
> <doc lang="en">http://foo.bar/doc/index.html</doc> |
28 |
> <doc lang="de">http://foo.bar/doc/index.de.html</doc> |
29 |
> <bugs-to>https://bugs.foo.bar</bugs-to> |
30 |
> <remote-id type="freshmeat">foobar</remote-id> |
31 |
> <remote-id type="sourceforge">foobar</remote-id> |
32 |
> </upstream> |
33 |
> |
34 |
> Please note: |
35 |
> - the <maintainer> tag in <upstream> is only for specifying an upstream |
36 |
> maintainer name and e-mail address and does not specify the ebuild |
37 |
> maintainer (although it may be the same if you decide to become |
38 |
> upstream). |
39 |
> - the type attribute for <remote-id> is currently one of (freshmeat| |
40 |
> sourceforge|cpan|vim), send a mail to gentoo-dev before adding |
41 |
> additional sites |
42 |
> - the data in the <remote-id> tags is an id which uniquely identifies |
43 |
> the project on that site: |
44 |
> - for type="vim": the script_id (example: 2586) |
45 |
> - for type="freshmeat": the project name (example: aria2) |
46 |
> - for type="sourceforge": the project name (example: liferea) |
47 |
> - for type="cpan": the module name (example: Pod-Index) |
48 |
|
49 |
Other sites I'd like to add: |
50 |
- pypi |
51 |
- google-code |
52 |
- ctan ... if someone can identify a key for packages |
53 |
|
54 |
Opinions? |
55 |
|
56 |
Cheers, |
57 |
Tiziano |
58 |
|
59 |
-- |
60 |
Tiziano Müller |
61 |
Gentoo Linux Developer |
62 |
Areas of responsibility: |
63 |
Samba, PostgreSQL, CPP, Python, sysadmin, GLEP Editor |
64 |
E-Mail : dev-zero@g.o |
65 |
GnuPG FP : F327 283A E769 2E36 18D5 4DE2 1B05 6A63 AE9C 1E30 |