external/aurweb
0
0
Fork 0
mirror of https://gitlab.archlinux.org/archlinux/aurweb.git synced 2025-02-03 10:43:03 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

updated to version 1.0.5 of the guidelines, closing bug #2850

Browse source
This commit is contained in:
pjmattal 2005-04-22 04:23:52 +00:00
parent dd51db3cc9
commit 6cf28ee18d
1 changed files with 5 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
web/html/guidelines.html
View file

@ -12,8 +12,8 @@
<body> <body>
<h1>AUR Guidelines</h1> <h1>AUR Guidelines</h1>
<div class="date">April 10, 2005</div> <div class="date">April 15, 2005</div>
<div class="version">1.0.0</div> <div class="version">1.0.2</div>
<address> <address>
Ben Mazer Ben Mazer
@ -113,7 +113,7 @@
<p> <p>
Follow these instructions for uploading/modifying packages: Follow these instructions for uploading/modifying packages:
<ol> <ol>
<li>Install the "tupkg" package.</li> <li>Install the "aurtools" package.</li>
<li>Email Jason (<a class='email' href="mailto:jason@archlinux.org">jason@archlinux.org</a>) for a CVS account.</li> <li>Email Jason (<a class='email' href="mailto:jason@archlinux.org">jason@archlinux.org</a>) for a CVS account.</li>
<li>Run the following commands to checkout the AUR CVS:<br /> <li>Run the following commands to checkout the AUR CVS:<br />
<kbd> <kbd>
@ -144,7 +144,8 @@
<h3 id='disowning'>Disowning packages</h3> <h3 id='disowning'>Disowning packages</h3>
<p> <p>
If a TU can't or doesn't want to maintain a package any longer, a notice should be posted to the AUR Mailing List, so another TU can maintain it. A package can still be disowned even if no other TU wants to maintain it, but the TUs should try not to drop many packages (they shouldn't take on more than they have time for). If a package has become obsolete or isn't used any longer, it can be removed completely as well. If a TU can't or doesn't want to maintain a package any longer, a notice should be posted to the AUR Mailing List, so another TU can maintain it. A package can still be disowned even if no other TU wants to maintain it, but the TUs should try not to drop many packages (they shouldn't take on more than they have time for). If a package has become obsolete or isn't used any longer, it can be removed completely as well. <br /><br />
If a package has been removed completely, it can be uploaded once again (fresh) to UNSUPPORTED, where a regular user can maintain the package instead of the TU.
</p> </p>
<h3 id="pkgguidelines">Packaging Etiquette</h3> <h3 id="pkgguidelines">Packaging Etiquette</h3>
<p> <p>