Remove mention of CVS and instead point to Subversion
No binary (build failed)
—
(log yok)
| @@ -138,7 +138,7 @@ have additions to this FAQ document, we would love to add them, | |
| An easy method to build your own basic BusyBox based system, is to | |
| follow these simple steps: | |
| <ul> | |
| - | <li> Point your web browser <a href="/cgi-bin/cvsweb/buildroot/">here</a> |
| + | <li> Point your web browser <a href="/cgi-bin/viewcvs.cgi/trunk/buildroot/">here</a> |
| <li> Click on "Download tarball" | |
| <li> Unpack the tarball on your Linux system somewhere | |
| <li> run 'make' and configure things to taste. | |
| @@ -1,57 +0,0 @@ | |
| - | <!--#include file="header.html" --> |
| - | |
| - | |
| - | <h3>Anonymous CVS</h3> |
| - | |
| - | We allow anonymous (read-only) CVS access to everyone. The first command you |
| - | need to run for anonymous CVS access is: |
| - | <pre> |
| - | cvs -d:pserver:[email protected]:/var/cvs login</pre> |
| - | <p> |
| - | CVS will prompt you for a password. Just press the Enter key (there is no |
| - | password for anonymous access). This step only needs to be done once, the first |
| - | time you attempt to access CVS. |
| - | <p> |
| - | Once the login is complete, you can then check the list of available |
| - | CVS modules by running the following command (all on one line): |
| - | <pre> |
| - | cvs -z3 -d:pserver:[email protected]:/var/cvs co -c </pre> |
| - | |
| - | <p> |
| - | If you wish, you can then check out a local copy of any of the |
| - | available modules. The following is an example of how to grab |
| - | a copy of busybox and tinylogin: |
| - | <pre> |
| - | cvs -z3 -d:pserver:[email protected]:/var/cvs co -P busybox tinylogin</pre> |
| - | This will create a directory called <b>busybox</b> and a directory called |
| - | <b>tinylogin</b> in the current directory. These directories contain the |
| - | latest and greatest source code for busybox and tinylogin. |
| - | |
| - | <p> |
| - | If you are not already familiar with using CVS, I recommend you visit |
| - | this quick <a href="/cvs_howto.html">Introduction to CVS</a>. |
| - | |
| - | <p> |
| - | I usually create a ~/.cvsrc file with the following things in it, and I |
| - | recommend you should use the same: |
| - | <pre> |
| - | -z3 |
| - | update -dP |
| - | rdiff -u |
| - | diff -ubBwpN |
| - | checkout -P</pre> |
| - | |
| - | <p> |
| - | Once you've checked out a copy of the source tree, you can update your |
| - | source tree at any time so it is in sync with the latest and greatest by |
| - | running the command: |
| - | <pre> |
| - | cvs update</pre> |
| - | |
| - | Because you've only been granted anonymous access to the tree, you won't be |
| - | able to commit any changes. Changes can be submitted for inclusion by posting |
| - | them to the appropriate mailing list. For those that are actively contributing |
| - | <a href="cvs_write.html">CVS write access</a> can be made available. |
| - | |
| - | <!--#include file="footer.html" --> |
| - | |
| @@ -1,44 +0,0 @@ | |
| - | <!--#include file="header.html" --> |
| - | |
| - | |
| - | <h3>How to use CVS</h3> |
| - | |
| - | |
| - | If you want to know all the gory details, you will want to visit |
| - | <a href="http://www.cvshome.org/">the CVS main web page</a>.<p> |
| - | For the impatient, the following is probably about all you need to know: |
| - | <p> |
| - | |
| - | <dl> |
| - | <dt><pre>cvs checkout -c</pre> |
| - | <dd>Will list the modules available for checkout |
| - | <dt><pre>cvs checkout < module name ></pre> |
| - | <dd>Will checkout the named module |
| - | <dt><pre>cvs co < module name ></pre> |
| - | <dd>Same thing |
| - | <dt><pre>cvs update</pre> |
| - | |
| - | <dd>Updates your local archive so it is in sync with the repository |
| - | -- your local updates are left intact. Tries to merge upstream updates |
| - | into your local updates. You will see the following tags when it is |
| - | updating your local repository: C means conflict, U means update, |
| - | P means patched, and M means modified. |
| - | <dt><pre>cvs up</pre> |
| - | <dd>Same thing |
| - | <dt><pre>cvs update < file name ></pre> |
| - | <dd>Same thing but for just the named file(s)/directory(s). |
| - | <dt><pre>cvs commit</pre> |
| - | <dd>Will check in all your work. |
| - | <dt><pre>cvs add < file name ></pre> |
| - | |
| - | <dd>Adds the named file/directory into CVS |
| - | <dt><pre>cvs remove < file name ></pre> |
| - | <dd>Removes the named file/directory from the upstream repository. |
| - | <dt><pre>cvs rm < file name ></pre> |
| - | <dd>Same thing |
| - | <dt><pre>cvs log < file name ></pre> |
| - | </dl> |
| - | |
| - | |
| - | <!--#include file="footer.html" --> |
| - | |
| @@ -1,32 +0,0 @@ | |
| - | <!--#include file="header.html" --> |
| - | |
| - | |
| - | <h3>CVS Read/Write Access</h3> |
| - | |
| - | If you want to be able to commit things to CVS, first contribute some |
| - | stuff to show you are serious. Then, very nicely ask |
| - | <a href="mailto:[email protected]">Erik Andersen</a> if he will set you up with |
| - | an account. To access CVS, you will want to add the following to set up your environment: |
| - | <pre> |
| - | $ export CVS_RSH=/usr/bin/ssh |
| - | $ export CVSROOT='[email protected]:/var/cvs'</pre> |
| - | <br> |
| - | It goes without saying you must change <em>username</em> to your own |
| - | username... |
| - | <p> |
| - | |
| - | To obtain commit access, you will need to demonstrate you are |
| - | serious by submitting a few good patches first. Then, you will need to |
| - | select a user-name to use when committing stuff, and finally, you will |
| - | need to send me the username you have selected, an ssh key, and the email |
| - | address where you prefer email to be sent (I will forward any email sent |
| - | to you, but not store it). |
| - | |
| - | <p> |
| - | Note that if you would prefer to keep your communications with me |
| - | private, you can encrypt your email using my |
| - | <a href="http://www.codepoet.org/andersen/erik/gpg.asc">public key</a>. |
| - | |
| - | <!--#include file="footer.html" --> |
| - | |
| - | |
| @@ -0,0 +1,58 @@ | |
| + | <!--#include file="header.html" --> |
| + | |
| + | |
| + | <h3>Subversion Read/Write Access</h3> |
| + | |
| + | If you want to be able to commit things to Subversion, first contribute some |
| + | stuff to show you are serious. Then, very nicely ask <a |
| + | href="mailto:[email protected]">Erik Andersen</a> if he will set you up |
| + | with an commit access to the Subversion repository. To access Subversion, you |
| + | will want to add the following to set up your environment: |
| + | |
| + | <p> |
| + | |
| + | To obtain commit access, you will need to demonstrate you are serious by |
| + | submitting a few good patches first. Then, you will need to select a username |
| + | to use when committing stuff, and finally, you will need to send me the |
| + | username you have selected, an ssh key, and the email address where you prefer |
| + | email to be sent (I will forward any email sent to you, but not store it). |
| + | |
| + | <p> |
| + | |
| + | Note that if you would prefer to keep your communications with me |
| + | private, you can encrypt your email using my |
| + | <a href="http://www.codepoet.org/andersen/erik/gpg.asc">public key</a>. |
| + | |
| + | <p> |
| + | |
| + | Once you are setup with an account, you will need to use your account to |
| + | checkout a copy of uClibc from Subversion: |
| + | |
| + | <pre> |
| + | svn list svn+ssh://[email protected]//svn/trunk/uClibc</pre> |
| + | <br> |
| + | It goes without saying you must change <em>username</em> to your own |
| + | username... |
| + | <p> |
| + | |
| + | You can then enter the newly checked out uClibc directory, make changes, check |
| + | your changes, diff your changes, revert your changes, and and commit your |
| + | changes usine commands such as: |
| + | |
| + | <pre> |
| + | svn diff |
| + | svn status |
| + | svn revert |
| + | svn commit</pre> |
| + | |
| + | <p> |
| + | |
| + | For additional detail on how to use Subversion, please visit the |
| + | <a href="http://subversion.tigris.org/">the Subversion website</a>. |
| + | You might also want to read online or buy a copy of <a |
| + | href="http://svnbook.red-bean.com/">the Subversion Book</a>... |
| + | |
| + | |
| + | <!--#include file="footer.html" --> |
| + | |
| + | |
| @@ -9,22 +9,18 @@ downloaded from <a href="downloads">http://www.busybox.net/downloads</a>. | |
| <p> | |
| You can also obtain <a href= "downloads/snapshots/">Daily Snapshots</a> of | |
| - | the latest CVS source tree. |
| + | the latest development source tree for those wishing to follow BusyBox development, |
| + | but cannot or do not wish to use Subversion (svn). |
| <ul> | |
| - | <li> Click here to browse the <a href="/cgi-bin/cvsweb/busybox/"> |
| - | CVS tree for the 1.00 stable version of BusyBox</a> |
| + | <li> Click here to <a href="/cgi-bin/viewcvs.cgi/trunk/busybox/">browse the source tree</a>. |
| </li> | |
| - | <li>Click here to browse the <a href="/cgi-bin/cvsweb/busybox.stable/"> |
| - | CVS tree for the old 0.60.x BusyBox version</a>. |
| + | <li>Anonymous <a href="subversion.html">Subversion access</a> is available. |
| </li> | |
| - | <li>Anonymous <a href="cvs_anon.html">CVS access</a> is available. |
| - | </li> |
| - | |
| - | <li>For those that are actively contributing there is |
| - | even <a href="cvs_write.html">CVS write access</a>. |
| + | <li>For those that are actively contributing obtaining |
| + | <a href="developer.html">Subversion read/write access</a> is also possible. |
| </li> | |
| </ul> | |
| @@ -9,9 +9,9 @@ | |
| <p> | |
| <font face="arial, helvetica, sans-serif" size="-1"> | |
| - | <a HREF="/copyright.txt">Copyright © 1999-2003 Erik Andersen</a> |
| + | <a HREF="/copyright.txt">Copyright © 1999-2005 Erik Andersen</a> |
| <br> | |
| - | Mail all comments, insults, suggestions and bribes to |
| + | Mail all comments, insults, suggestions and bribes to |
| <br> | |
| Erik Andersen <A HREF="mailto:[email protected]">[email protected]</A><BR> | |
| </font> | |
| @@ -48,10 +48,10 @@ | |
| <br><a href="/lists.html">Mailing Lists</a> | |
| <br><a href="/news.html">Latest News</a> | |
| <br><a href="/download.html">Download</a> | |
| - | <br><a href="/FAQ.html">FAQ</a> |
| - | <br><a href="/cvs_anon.html">Accessing CVS</a> |
| - | <br><a href="/cgi-bin/cvsweb/busybox/">Browse CVS</a> |
| + | <br><a href="/cgi-bin/viewcvs.cgi/trunk/busybox/">Browse Source</a> |
| + | <br><a href="/subversion.html">Accessing Source</a> |
| <br><a href="http://bugs.busybox.net/">Bug Tracking</a> | |
| + | <br><a href="/FAQ.html">FAQ</a> |
| <br><a href="/docs.html">Documentation</a> | |
| <br><a href="/products.html">Products</a> | |
| <br><a href="/shame.html">Hall of Shame</a> | |
| @@ -15,7 +15,8 @@ There is also a mailing list for <a href="/lists/busybox-cvs/">active developers | |
| wishing to read the complete diff of each and every change to busybox -- not for the | |
| faint of heart. Active developers can subscribe by visiting | |
| <a href="http://codepoet.org/mailman/listinfo/busybox-cvs">this page</a>. | |
| - | The CVS server is the only one permtted to post to this list. |
| + | The Subversion server is the only one permtted to post to this list. And yes, |
| + | this list name uses the word 'cvs' even though we don't use that anymore... |
| <p> | |
| @@ -888,7 +888,7 @@ image</a>. Here's how you use it: | |
| Also, some exciting infrastructure news! Busybox now has its own | |
| <a href="lists/busybox/">mailing list</a>, | |
| publically browsable | |
| - | <a href="/cgi-bin/cvsweb/busybox/">CVS tree</a>, |
| + | <a href="/cgi-bin/viewcvs.cgi/trunk/busybox/">CVS tree</a>, |
| anonymous | |
| <a href="cvs_anon.html">CVS access</a>, and | |
| for those that are actively contributing there is even | |
| @@ -13,7 +13,7 @@ listed in the order I happen to add them to the web page: | |
| <ul> | |
| - | <li><a href="/cgi-bin/cvsweb/buildroot/">buildroot</a><br>A configurable |
| + | <li><a href="/cgi-bin/viewcvs.cgi/trunk/buildroot/">buildroot</a><br>A configurable |
| means for building your own busybox/uClibc based system systems. | |
| <li><a href="http://www.pengutronix.de/software/ptxdist_en.html">PTXdist</a><br>another | |
| @@ -0,0 +1,38 @@ | |
| + | <!--#include file="header.html" --> |
| + | |
| + | |
| + | <h3>Anonymous Subversion Access</h3> |
| + | |
| + | We allow anonymous (read-only) Subversion (svn) access to everyone. To |
| + | grab a copy of the latest version of uClibc using anonymous svn access is: |
| + | |
| + | <pre> |
| + | svn co svn://www.uclibc.org/trunk/uClibc</pre> |
| + | |
| + | |
| + | <p> |
| + | |
| + | If you are not already familiar with using Subversion, I recommend you visit <a |
| + | href="http://subversion.tigris.org/">the Subversion website</a>. You might |
| + | also want to read online or buy a copy of <a |
| + | href="http://svnbook.red-bean.com/">the Subversion Book</a>. If you are |
| + | already comfortable with using CVS, you may want to skip ahead to the <a |
| + | href="http://svnbook.red-bean.com/en/1.1/apa.html">Subversion for CVS Users</a> |
| + | part of the Subversion Book. |
| + | |
| + | <p> |
| + | |
| + | Once you've checked out a copy of the source tree, you can update your source |
| + | tree at any time so it is in sync with the latest and greatest by entering your |
| + | uClibc directory and running the command: |
| + | |
| + | <pre> |
| + | svn update</pre> |
| + | |
| + | Because you've only been granted anonymous access to the tree, you won't be |
| + | able to commit any changes. Changes can be submitted for inclusion by posting |
| + | them to the uClibc mailing list. For those that are actively contributing |
| + | <a href="developer.html">Subversion commit access</a> can be made available. |
| + | |
| + | <!--#include file="footer.html" --> |
| + | |