| File: arch.txt | |
|---|---|
| patch-10 | patch-11 |
| Line 11 | Line 11 |
| * <http://wiki.gnuarch.org/moin.cgi/Learning_20Arch_20commands_20for_20CVS_20users Arch commands for CVS users> * <http://wiki.gnuarch.org/moin.cgi/Glossary the arch glossary> | * <http://wiki.gnuarch.org/moin.cgi/Learning_20Arch_20commands_20for_20CVS_20users Arch commands for CVS users> * <http://wiki.gnuarch.org/moin.cgi/Glossary the arch glossary> |
| So <http://wiki.gnuarch.org/moin.cgi/Getting_20Arch download arch> and start reading this tutorial. We hope to keep it strictly relevant to the lnx-bbc project. | |
| = Arch for core LNX-BBC developers = This section assumes that you have a gargoyle account and are in the src | = Arch for core LNX-BBC developers = This section assumes that you have a gargoyle account and are in the src |
| Line 53 | Line 57 |
| signature! Thus, there are a few steps to take before you begin working with the official branches. | signature! Thus, there are a few steps to take before you begin working with the official branches. |
| Also, you ought to have gnupg 1.2 or better in order to have the keyserver functions we make use of. If you're running debian stable, consider adding the following line to your /etc/apt/sources.list: ----8<---- deb http://www.backports.org/debian stable tla gnupg ----8<---- This is how gargoyle gets its copies of arch and gpg. | |
| === Make a key === We plan to generate a keyring just for the lnx-bbc project, and use that to | === Make a key === We plan to generate a keyring just for the lnx-bbc project, and use that to |
| verify changeset signatures. We recommend using your @lnx-bbc.org address (the username is your username on gargoyle), since it is somewhat of a role account. | verify changeset signatures. You ought to make a fresh new key for the lnx-bbc project. We recommend using your @lnx-bbc.org address (the username is your username on gargoyle), since it is somewhat of a role account. |
| ----8<---- $ gpg --gen-key | ----8<---- $ gpg --gen-key |
| Line 330 | Line 344 |
| == moving files == | == moving files == |
| Arch has the "tla mv" command, which allows you to move a file from one place in a branch to another, retaining its revision history! | Arch has the "tla mv" command, which allows you to move a file from one place in a branch to another, retaining its revision history! == Speeding up remote operations == Arch uses SFTP as the remote protocol, and it's low-level enough that serious lag can be introduced while talking with gargoyle. To speed things up, you can create a local cache of individual files in the archive, otherwise known as a *library*. ----8<---- $ mkdir ~/.arch-library $ tla my-revision-library ~/.arch-library/ $ tla library-config --greedy ~/.arch-library/ $ tla library-add lnx-bbc-devel@zork.net--gar-autobuild/lnx-bbc--research--0.0 $ tla library-add lnx-bbc-devel@zork.net--gar-autobuild/lnx-bbc--stable--2.1 ----8<---- What you will now have is a greedy library that will automatically cache unpacked versions of all the files in those two branches you library-added. |
| == Public mirrors == | == Public mirrors == |