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

some fixes in beta manifest

Browse source
This commit is contained in:
pjmattal 2005-02-23 04:34:19 +00:00
parent 03ec762532
commit aa8135655a
1 changed files with 33 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

42
web/html/beta.html
View file

@ -136,30 +136,54 @@ step is necessary so we can make sure that the right people are getting
the right access. We will migrate this information to the production the right access. We will migrate this information to the production
system, so you won't have to do it again.<br> system, so you won't have to do it again.<br>
</li> </li>
<li>Check out the CVS tree for the AUR repository, located at:<br> <li>Check out the CVS tree for the AUR repository. To do this,
<code>:pserver:&lt;userid&gt;@cvs.archlinux.org/home/cvs-aur-test</code><br> execute the following commands:<br>
<br>
<code>export
CVSROOT=":pserver:&lt;userid&gt;@cvs.archlinux.org:/home/cvs-aur-test"<br>
cvs login<br>
cvs co aur-test</code><br>
<br>
If you're If you're
a TU or developer, you should already have an account in this new a TU, you should already have an account in this new
repository.</li> repository. If you are a developer, email Jason (jason at archlinux dot
org) and he'll set up access for you.<br>
</li>
<li>Build binary packages for things you wish to place in the AUR, <li>Build binary packages for things you wish to place in the AUR,
and add the PKGBUILD and accompanying necessary files to the CVS and add the PKGBUILD and accompanying necessary files to the CVS
repository.<br> repository. You can do this with:<br>
<br>
<code>cvs add &lt;directory&gt;<br>
cd &lt;directory&gt;<br>
cvs add PKGBUILD<br>
.<br>
.<br>
cvs commit</code><br>
<br>
</li> </li>
<li>Upload the binary packages using the "tupkg" tool. Run<span <li>Upload the binary packages using the "tupkg" tool. Run<span
style="font-family: monospace;">:<br> style="font-family: monospace;">:<br>
</span><code>tupkg </span><code><br>
tupkg
--host --host
subzero.elys.com --user &lt;userid&gt; --password &lt;password&gt; subzero.elys.com --user &lt;userid&gt; --password &lt;password&gt;
&lt;packagefile.pkg.tar.gz&gt;</code><br> &lt;packagefile.pkg.tar.gz&gt;</code><br>
<br>
Note that this is your <span style="font-weight: bold;">AUR login Note that this is your <span style="font-weight: bold;">AUR login
password</span> not your CVS password, in case they are different.<br> password</span> -- the one you assign when you create your account, not
your CVS password, in case they are different.<br>
</li> </li>
<li>Once your packages are uploaded successfully, tag the newly <li>Once your packages are uploaded successfully, tag the newly
created package files with the CURRENT tag in cvs.</li> created package files with the CURRENT tag in cvs. You can do this with:<br>
<code><br>
cvs tag -cFR CURRENT &lt;newpackagebuilddir&gt;</code> <br>
<br>
</li>
<li>In 5-10 minutes, the automated script will add them to the AUR <li>In 5-10 minutes, the automated script will add them to the AUR
repository. Verify that they appear both in the web interface and repository. Verify that they appear both in the web interface and
become become
available via pacman -S from the aur repository.</li> available via <code>pacman -Sy &lt;package&gt;</code> from the aur
repository.</li>
<li>Select the newly added or updated package in the AUR web <li>Select the newly added or updated package in the AUR web
interface and set yourself as the maintainer.<br> interface and set yourself as the maintainer.<br>
</li> </li>