Line 142
Link Here
|
|
|
142 |
<ti><brite><upstream></brite></ti> |
143 |
<ti> |
144 |
This tag contains information about the upstream developers/project. |
145 |
</ti> |
146 |
</tr> |
147 |
<tr> |
148 |
<ti><brite><maintainer></brite></ti> |
149 |
<ti> |
150 |
Name and e-mail of an upstream maintainer. May appear more than once. |
151 |
</ti> |
152 |
</tr> |
153 |
<tr> |
154 |
<ti><brite><name></brite></ti> |
155 |
<ti> |
156 |
The name of an usptream maintainer should contain a block of text with upstream's name. |
157 |
This element is mandatory for an upstream maintainer and must appear only once. |
158 |
</ti> |
159 |
</tr> |
160 |
<tr> |
161 |
<ti><brite><email></brite></ti> |
162 |
<ti> |
163 |
The email address of an upstream may appear only once. |
164 |
</ti> |
165 |
</tr> |
166 |
<tr> |
167 |
<ti><brite><changelog></brite></ti> |
168 |
<ti> |
169 |
Should contain a URL where the location of the upstream changelog can be found. |
170 |
The URL must be version independent and must point to a changelog which is only |
171 |
updated on new releases of the corresponding package. (This also implies that |
172 |
one can link to an automatically updated changelog in case of vcs snapshots |
173 |
only.) |
174 |
</ti> |
175 |
</tr> |
176 |
<tr> |
177 |
<ti><brite><doc></brite></ti> |
178 |
<ti> |
179 |
Should contain a URL where the location of the upstream documentation can be |
180 |
found. The link must not point to any third party documentation and must be |
181 |
version independent. If the documentation is available in more than one language, |
182 |
a lang attribute can be used which follows the same rules as the one for |
183 |
longdescription. |
184 |
</ti> |
185 |
</tr> |
186 |
<tr> |
187 |
<ti><brite><bugs-to></brite></ti> |
188 |
<ti> |
189 |
Should contain a place where bugs can be filed, a URL or an e-mail address prefixed |
190 |
with mailto:. |
191 |
</ti> |
192 |
</tr> |
193 |
<tr> |
194 |
<ti><brite><remote-id></brite></ti> |
195 |
<ti> |
196 |
Should specify a type of package identification tracker and the identification that |
197 |
corresponds to the package in question. remote-id should make it easier to index |
198 |
information such as its Freshmeat ID or its CPAN name. |
199 |
</ti> |
200 |
</tr> |
201 |
<tr> |
Line 171
Link Here
|
171 |
<brite><use></brite> |
231 |
<brite><use></brite>, <brite><doc></brite> |
172 |
-- |
|
|
Line 215
Link Here
|
|
|
275 |
<tr> |
276 |
<ti>status</ti> |
277 |
<ti> |
278 |
<brite><maintainer></brite> |
279 |
</ti> |
280 |
<ti> |
281 |
The upstream maintainer element has a status attribute, which is one of active or inactive. |
282 |
This attribute is not mandatory. The absence of it shall be interpreted as unknown. |
283 |
Please note: This attribute is only allowed in the <upstream> <maintainer> element! |
284 |
</ti> |
285 |
</tr> |
286 |
<tr> |
287 |
<ti>type</ti> |
288 |
<ti> |
289 |
<brite><remote-id></brite> |
290 |
</ti> |
291 |
<ti> |
292 |
A string identifying the type of upstream source. A list of valid strings are kept in metadata.dtd. |
293 |
Developers should email the gentoo-dev mailing list before using a new type value. |
294 |
</ti> |
295 |
</tr> |
296 |
|
Line 360
Link Here
|
|
|
442 |
|
443 |
<subsection> |
444 |
<title>Fourth Example</title> |
445 |
<body> |
446 |
|
447 |
<p> |
448 |
This example demonstrates the usage of the upstream element |
449 |
</p> |
450 |
|
451 |
<pre caption="Upstream description"> |
452 |
<upstream> |
453 |
<maintainer status="inactive"> |
454 |
<name>Foo Bar</name> |
455 |
<email>foo@bar.bar</email> |
456 |
</maintainer> |
457 |
<maintainer status="active"> |
458 |
<name>Foo Gentoo</name> |
459 |
<email>foo@gentoo.org</email> |
460 |
</maintainer> |
461 |
<changelog>http://foo.bar/changelog.txt</changelog> |
462 |
<doc lang="en">http://foo.bar/doc/index.html</doc> |
463 |
<doc lang="de">http://foo.bar/doc/index.de.html</doc> |
464 |
<bugs-to>https://bugs.foo.bar</bugs-to> |
465 |
<remote-id type="freshmeat">foobar</remote-id> |
466 |
<remote-id type="sourceforge">foobar</remote-id> |
467 |
</upstream> |
468 |
</pre> |
469 |
|
470 |
</subsection> |
471 |
|