uClibc

About
Latest News
Download
FAQ
Mailing Lists
Developing
Browse Source
Bug Tracking
Toolchains
Products
Other libcs

Anonymous Subversion Access

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:

svn co svn://uclibc.org/trunk/uClibc

If you are not already familiar with using Subversion, I recommend you visit the Subversion website. You might also want to read online or buy a copy of the Subversion Book. If you are already comfortable with using CVS, you may want to skip ahead to the Subversion for CVS Users part of the Subversion Book.

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:

svn update

Because you've only been granted anonymous access to the tree, you won't be able to commit any changes.

Contributing

So you've made some changes and you would like to contribute them back. Great! The way we handle this is via our Mailing Lists. Just sign up to the dev mailing list, describe the changes (what/why/how/etc...), and include your patch.

Things to keep in mind when submitting your patches:

Too much information is better than not enough!
If you post patches inline, please turn off word wrapping and other such e-mail mangling "features"
If you attach patches, please make sure you flag them as "automatic display"
Do not compress patches (the list currently has 100k limit)
Please include a "Signed-off-by" line

New Developers

To obtain commit access, you will need to demonstrate you are serious by submitting a few good patches first. This is accomplished via our Mailing Lists. So you've contributed quite a bit and you're still here? Let's move on then!

There's the fun logistic issues to work out first, so here's the new developer check list:

Your preferred username for committing to the server
Your preferred e-mail address for contact
Your public ssh key (should be ssh version 2 DSA key with 1024 bits (the default) or more)

If you do not have a public ssh key, then you can easily generate one. Simply use the command:

ssh-keygen -t dsa

This will output the files id_dsa (your private key -- do not give this to anyone!) and id_dsa.pub (your public key -- give this to me). By default, both files will be placed in your home directory in the .ssh subdir.

While not required, you should also create an account on our Bug Tracker. When you have, simply e-mail me the username on the tracker so that you can have your account settings changed from the default "reporter" to "developer" (this allows you to make changes to all bug reports).

Committing

Once you are setup with an account, you will need to use your account to checkout a copy of uClibc:

svn list svn+ssh://username@svn.uclibc.org/svn/trunk/uClibc

It goes without saying you must change username to your own username... For the adventurous, you could set the username in your ~/.ssh/config file as well of course.

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 using commands such as:

svn log
svn diff
svn status
svn revert
svn commit

For additional detail on how to use Subversion, please visit the the Subversion website. You might also want to read online or buy a copy of the Subversion Book...

Other Services

Now that you have an account on the server, there's a few things you are given access to for free.

shell: simply ssh to username@uclibc.org
e-mail: username@uclibc.org (you can forward this by using ~/.forward)
web: http://uclibc.org/~username/ (this is your ~/public_html/ directory)

If you have any other questions, feel free to post them to the list.