diff options
| -rw-r--r-- | docs/uclibc.org/FAQ.html | 8 | ||||
| -rw-r--r-- | docs/uclibc.org/cvs_anon.html | 57 | ||||
| -rw-r--r-- | docs/uclibc.org/cvs_howto.html | 44 | ||||
| -rw-r--r-- | docs/uclibc.org/cvs_write.html | 32 | ||||
| -rw-r--r-- | docs/uclibc.org/developer.html | 58 | ||||
| -rw-r--r-- | docs/uclibc.org/download.html | 15 | ||||
| -rw-r--r-- | docs/uclibc.org/header.html | 4 | ||||
| -rw-r--r-- | docs/uclibc.org/lists.html | 3 | ||||
| -rw-r--r-- | docs/uclibc.org/oldnews.html | 24 | ||||
| -rw-r--r-- | docs/uclibc.org/products.html | 2 | ||||
| -rw-r--r-- | docs/uclibc.org/subversion.html | 38 | ||||
| -rw-r--r-- | docs/uclibc.org/toolchains.html | 6 |
12 files changed, 127 insertions, 164 deletions
diff --git a/docs/uclibc.org/FAQ.html b/docs/uclibc.org/FAQ.html index 6826e2f54..0f400a43b 100644 --- a/docs/uclibc.org/FAQ.html +++ b/docs/uclibc.org/FAQ.html @@ -229,13 +229,13 @@ How could it be smaller and not suck?</a></h2> <a href="http://gcc.gnu.org/">the gcc compiler</a>, and uClibc, all built to produce binaries for your target system linked with uClibc. You can build your own native uClibc toolchain using the - <a href="/cgi-bin/cvsweb/buildroot/">uClibc buildroot system</a>. + <a href="/cgi-bin/viewcvs.cgi/trunk/buildroot/">uClibc buildroot system</a>. <p> To build your own uClibc toolchain, follow the following 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> Edit the Makefile as needed if you wish to change anything. @@ -265,7 +265,7 @@ How could it be smaller and not suck?</a></h2> We used to provide a toolchain wrapper, but that has been removed due to numerous problems. The uClibc developers have gone to a lot of trouble to produce the - <a href="/cgi-bin/cvsweb/buildroot/">uClibc buildroot system</a>, + <a href="/cgi-bin/viewcvs.cgi/trunk/buildroot/">uClibc buildroot system</a>, which makes it easy to build your own uClibc toolchain and/or an initial uClibc based system. @@ -332,7 +332,7 @@ How could it be smaller and not suck?</a></h2> <p> Each of these uClibc development systems was created using - <a href="/cgi-bin/cvsweb/buildroot/">buildroot</a>, specifically, + <a href="/cgi-bin/viewcvs.cgi/trunk/buildroot/">buildroot</a>, specifically, <a href="http://www.uclibc.org/downloads/buildroot.tar.bz2">buildroot.tar.bz2</a> along with <a href="http://www.uclibc.org/downloads/buildroot-sources">these sources</a>. diff --git a/docs/uclibc.org/cvs_anon.html b/docs/uclibc.org/cvs_anon.html deleted file mode 100644 index e5ed5b80a..000000000 --- a/docs/uclibc.org/cvs_anon.html +++ /dev/null @@ -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:anonymous@uclibc.org:/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:anonymous@uclibc.org:/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 uClibc: -<pre> - cvs -z3 -d:pserver:anonymous@uclibc.org:/var/cvs co -P uClibc</pre> -This will create a directory called <b>uClibc</b> in the current -directory. This directory will contain the latest and greatest source -code for uClibc. - -<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" --> - diff --git a/docs/uclibc.org/cvs_howto.html b/docs/uclibc.org/cvs_howto.html deleted file mode 100644 index cff3a353c..000000000 --- a/docs/uclibc.org/cvs_howto.html +++ /dev/null @@ -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" --> - diff --git a/docs/uclibc.org/cvs_write.html b/docs/uclibc.org/cvs_write.html deleted file mode 100644 index dcaaec22b..000000000 --- a/docs/uclibc.org/cvs_write.html +++ /dev/null @@ -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:andersen@codepoet.org">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='username@cvs.uclibc.org:/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" --> - - diff --git a/docs/uclibc.org/developer.html b/docs/uclibc.org/developer.html new file mode 100644 index 000000000..215633c97 --- /dev/null +++ b/docs/uclibc.org/developer.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:andersen@codepoet.org">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://username@svn.uclibc.org//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" --> + + diff --git a/docs/uclibc.org/download.html b/docs/uclibc.org/download.html index cf888fc2f..6ecbc3aca 100644 --- a/docs/uclibc.org/download.html +++ b/docs/uclibc.org/download.html @@ -8,22 +8,21 @@ Source for the latest release can always be downloaded from <a href="downloads/">http://www.uclibc.org/downloads</a> <p> -You can also obtain <a href= "downloads/snapshots/">Daily Snapshots</a> of -the latest CVS source tree for those wishing to follow uClibc development, -but cannot or do not wish to use CVS. +You can also obtain <a href= "downloads/snapshots/">Daily Snapshots</a> of +the latest development source tree for those wishing to follow uClibc development, +but cannot or do not wish to use Subversion (svn). <p> <ul> - <li> Click here to <a href="/cgi-bin/cvsweb/uClibc/"> - browsable the CVS tree</a>. + <li> Click here to <a href="/cgi-bin/viewcvs.cgi/trunk/uClibc/">browse the source tree</a>. </li> - <li>Anonymous <a href="cvs_anon.html">CVS access</a> is available. + <li>Anonymous <a href="subversion.html">Subversion 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> diff --git a/docs/uclibc.org/header.html b/docs/uclibc.org/header.html index 9b4a80982..f16ec3056 100644 --- a/docs/uclibc.org/header.html +++ b/docs/uclibc.org/header.html @@ -47,8 +47,8 @@ <br><a href="/news.html">Latest News</a> <br><a href="/download.html">Download</a> <br><a href="/toolchains.html">Toolchains</a> - <br><a href="/cvs_anon.html">Accessing CVS</a> - <br><a href="/cgi-bin/cvsweb/uClibc/">Browse CVS</a> + <br><a href="/subversion.html">Accessing Source</a> + <br><a href="/cgi-bin/viewcvs.cgi/trunk/uClibc/">Browse Source</a> <br><a href="http://bugs.uclibc.org/">Bug Tracking</a> <br><a href="/products.html">Products</a> <br><a href="/other_libs.html">Other libcs</a> diff --git a/docs/uclibc.org/lists.html b/docs/uclibc.org/lists.html index 95a805fe4..dca492633 100644 --- a/docs/uclibc.org/lists.html +++ b/docs/uclibc.org/lists.html @@ -15,7 +15,8 @@ There is also a mailing list for <a href="/lists/uclibc-cvs/">active developers< wishing to read the complete diff of each and every change to uClibc -- not for the faint of heart. Active developers can subscribe by visiting <a href="http://codepoet.org/mailman/listinfo/uclibc-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> diff --git a/docs/uclibc.org/oldnews.html b/docs/uclibc.org/oldnews.html index 08fb47e24..06af6254c 100644 --- a/docs/uclibc.org/oldnews.html +++ b/docs/uclibc.org/oldnews.html @@ -175,7 +175,7 @@ available within a few days. Meanwhile, we invite you to try out uClibc with the latest <a href="http://ltp.sourceforge.net/">Linux Test Project test suite</a> (you will need to apply a small <a - href="http://www.uclibc.org/cgi-bin/cvsweb/buildroot/sources/ltp-testsuite.patch?rev=1.3">patch</a>. + href="http://www.uclibc.org/cgi-bin/viewcvs.cgi/trunk/buildroot/sources/ltp-testsuite.patch?rev=1.3">patch</a>. And also give the latest Perl and Python test suites a try as well. If you find any bugs in uClibc, PLEASE let us know! <p> @@ -221,7 +221,7 @@ them fill the drive. Whatever works for you. <p> If you would like to build your own custom uClibc system, you can - use <a href="/cgi-bin/cvsweb/buildroot/">buildroot</a>, which is + use <a href="/cgi-bin/viewcvs.cgi/trunk/buildroot/">buildroot</a>, which is how these uClibc development systems were created. <p> @@ -342,7 +342,7 @@ drive. Whatever works for you. <p> If you would like to build your own custom uClibc system, you can - use <a href="/cgi-bin/cvsweb/buildroot/">buildroot</a>, which is + use <a href="/cgi-bin/viewcvs.cgi/trunk/buildroot/">buildroot</a>, which is how the uClibc development systems were created. <p> @@ -537,7 +537,7 @@ <p> All three development system images were compiled and built using the stock - <a href="/cgi-bin/cvsweb/buildroot/">buildroot</a> system. These were also + <a href="/cgi-bin/viewcvs.cgi/trunk/buildroot/">buildroot</a> system. These were also built using the (about to be announced in a couple on minutes) uClibc 0.9.17 release, so if you want to begin compiling and testing stuff with uClibc, but you don't feel like spending the _hours_ it takes to download, @@ -551,7 +551,7 @@ <p> Oh, and I have also have updated the uClibc/gcc toolchain builders, so if you just want a simple uClibc/gcc toolchain, - <a href="/cgi-bin/cvsweb/toolchain/">one of these should work for you.</a> + <a href="/cgi-bin/viewcvs.cgi/trunk/toolchain/">one of these should work for you.</a> <p> @@ -574,7 +574,7 @@ <br> CodePoet Consulting (i.e. Erik) has been working hard on <a - href="/cgi-bin/cvsweb/buildroot/">buildroot</a> recently, and is pleased to + href="/cgi-bin/viewcvs.cgi/trunk/buildroot/">buildroot</a> recently, and is pleased to offer a full stand-alone uClibc-only development system. This is an ext2 filesystem for i386 containing all the development software you need to build your own uClibc applications. With bash, awk, make, gcc, g++, @@ -672,7 +672,7 @@ This toolchain should make it easy for anyone to build uClibc based applications. - <a href="/cgi-bin/cvsweb/toolchain/"> Source code can be downloaded here</a>. + <a href="/cgi-bin/viewcvs.cgi/trunk/toolchain/"> Source code can be downloaded here</a>. Be aware that much of the needed source code will actually be downloaded on when you compile the toolchains. To build a toolchain, simply grab the source, edit the Makefile to select where you would like @@ -749,7 +749,7 @@ This toolchain should make it easy for anyone to build uClibc based applications. - <a href="/cgi-bin/cvsweb/toolchain/">Source code can be downloaded here</a>. + <a href="/cgi-bin/viewcvs.cgi/trunk/toolchain/">Source code can be downloaded here</a>. Be aware that much of the needed source code will actually be downloaded on demand when you compile things. To build the toolchain, simply grab the source, edit the Makefile to select where you would like @@ -817,7 +817,7 @@ These toolchains should make it easy to anyone to build uClibc based applications. - <a href="/cgi-bin/cvsweb/toolchain/">Source code can be downloaded here</a>. + <a href="/cgi-bin/viewcvs.cgi/trunk/toolchain/">Source code can be downloaded here</a>. Be aware that much of the needed source code will actually be downloaded on demand when you compile things. To build the toolchain, simply grab the source, edit the Makefile to select where you would like @@ -853,7 +853,7 @@ gcc-3.1 toolchain that natively targets uClibc. Additionally, the gcc-3.0.4 and gcc-2.95 toolchains have also been updated. These toolchains make it easy to build uClibc based applications. - <a href="/cgi-bin/cvsweb/toolchain/">Source code can be downloaded here</a>. + <a href="/cgi-bin/viewcvs.cgi/trunk/toolchain/">Source code can be downloaded here</a>. and is now much smaller, since much of the needed binutils and gcc source code is now downloaded on demand. To build the toolchain, simply grab the source, edit the Makefile @@ -890,7 +890,7 @@ shortly, but is not yet ready. At this time, only source code and a Makefile for the native uClibc toolchain is being released (i.e. no binaries, sorry). - <a href="/cgi-bin/cvsweb/toolchain/">Source code can be downloaded here</a>. + <a href="/cgi-bin/viewcvs.cgi/trunk/toolchain/">Source code can be downloaded here</a>. <p> To build the toolchain, simply grab the source, edit the Makefile to select where you would like the toolchain installed. Then @@ -1017,7 +1017,7 @@ Those wanting an easy way to test out uClibc and give it a test drive can download and compile - <a href="/cgi-bin/cvsweb/buildroot/">buildroot</a>. + <a href="/cgi-bin/viewcvs.cgi/trunk/buildroot/">buildroot</a>. This is a nifty buildsystem that will automagically download and build a <a href="http://user-mode-linux.sourceforge.net/">User-Mode Linux</a> kernel, and will then download source for and compile up a fully diff --git a/docs/uclibc.org/products.html b/docs/uclibc.org/products.html index 797638400..58ce0b028 100644 --- a/docs/uclibc.org/products.html +++ b/docs/uclibc.org/products.html @@ -12,7 +12,7 @@ listed in the order I happen to add them to the web page: <ul> -<li><a href="/cgi-bin/cvsweb/buildroot/">buildroot</a> a configurable +<li><a href="/cgi-bin/viewcvs.cgi/trunk/buildroot/">buildroot</a> a configurable means for building your own busybox/uClibc based system systems. </li><li><a href="http://leaf.sourceforge.net/mod.php?mod=userpage&menu=910&page_id=36">LEAF Bering-uClibc</a> diff --git a/docs/uclibc.org/subversion.html b/docs/uclibc.org/subversion.html new file mode 100644 index 000000000..f7a4473bf --- /dev/null +++ b/docs/uclibc.org/subversion.html @@ -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" --> + diff --git a/docs/uclibc.org/toolchains.html b/docs/uclibc.org/toolchains.html index 376c8e634..b66d05f2b 100644 --- a/docs/uclibc.org/toolchains.html +++ b/docs/uclibc.org/toolchains.html @@ -7,13 +7,13 @@ of <a href="http://sources.redhat.com/binutils/">GNU binutils</a>, <a href="http://gcc.gnu.org/">the gcc compiler</a>, and uClibc, all built to produce binaries for your target system linked with uClibc. You can build your own native uClibc toolchain using the -<a href="/cgi-bin/cvsweb/buildroot/">uClibc buildroot system</a>. +<a href="/cgi-bin/viewcvs.cgi/trunk/buildroot/">uClibc buildroot system</a>. <p> To build your own uClibc toolchain, follow the following 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> Edit the Makefile as needed if you wish to change anything. @@ -61,7 +61,7 @@ strace, busybox, GNU coreutils, GNU tar, GNU grep, etc. <p> Each of these uClibc development systems was created using -<a href="/cgi-bin/cvsweb/buildroot/">buildroot</a>, specifically, +<a href="/cgi-bin/viewcvs.cgi/trunk/buildroot/">buildroot</a>, specifically, <a href="http://www.uclibc.org/downloads/buildroot.tar.bz2">buildroot.tar.bz2</a> along with <a href="http://www.uclibc.org/downloads/buildroot-sources">these sources</a>. |