Portable Linux Processor Affinity (PLPA): Subversion Checkout

Note that this project is deprecated by the Portable Hardware Locality (hwloc) project!

First, you will need a Subversion client. We recommend getting the latest version available. If you do not have the command "svn" in your path, you will likely need to download and install Subversion (note that you only need the Subversion client. Getting the server to compile may be quite complex and require a lot of dependencies -- the client is currently significantly easier to compile).

There are three general areas of the source code repository that will interest most users:

• Trunk: The trunk is generally the head of PLPA development. It is located in the directory /trunk in the repository.
• Branches: Major stable releases are always branched. For example, the 1.0 series of the PLPA will be available under the /branches/v1.0/ directory; the 1.1 series is available under /branches/v1.1/, etc. Hence, the head of development for a given series is available under its directory in /branches/.
• Tags: Point releases are all tagged under the /tags directory. For example, version 1.0.0 is available under /tags/v1.0.0/, version 1.0.1 is available under /tags/v1.0.1/, version 2.3.4 is available under /tags/v2.3.4, etc.

Anonymous, read-only access

The base URL of the PLPA Subversion repository is: http://svn.open-mpi.org/svn/plpa/. Use it to obtain a checkout of any portion of the repository. For example, to obtain a checkout of the trunk:

shell$ svn co http://svn.open-mpi.org/svn/plpa/trunk plpa-trunk
[...lots of output...]

The "list" Subversion command can be used to show which branches and tags are available:

shell$ svn list http://svn.open-mpi.org/svn/plpa/tags
[...list of the tag directories available...]

Note that Subversion is natively capable of using many forms of web proxies. If your network setup requires the user of a web proxy, consult the Subversion documentation for more details.

Authenticated access

Registered developers need to perform an authenticated checkout in order to be able to commit changes back to the repository. The procedure is identical to the anonymous, read-only checkout (detailed above) except that you should use "https" instead of "http":

shell$ svn co https://svn.open-mpi.org/svn/plpa/trunk plpa-trunk
[...lots of output...]

Note that the first time you perform an authenticated checkout on any machine, you will be prompted to accept svn.open-mpi.org's SSL certificate and to type in your Subversion username and password. For example:

shell$ svn co https://svn.open-mpi.org/svn/plpa/trunk plpa-trunk
Error validating server certificate for 'https://svn.open-mpi.org:443':
 - The certificate is not issued by a trusted authority. Use the
   fingerprint to validate the certificate manually!  Certificate information:
 - Hostname: svn.open-mpi.org
 - Valid: from Apr  4 13:52:48 2005 GMT until Apr  2 13:52:48 2015 GMT
 - Issuer: Computer Science Department, Indiana University,  Bloomington, Indiana, US
 - Fingerprint: 92:dd:79:e4:43:6f:d1:a3:11:68:7f:81:38:ab:39:c1:be:c2:fd:1c
(R)eject, accept (t)emporarily or accept (p)ermanently? 

If the fingerprint shown by your Subversion client matches what is displayed above, it is easiest to (p)ermanently accept the certificate (Subversion will warn you if the fingerprint ever changes).

Next, you'll be prompted for your password:

Authentication realm:  PLPA Subversion Access
Password for 'your_username':

If the username displayed does not match your Subversion registered username, simply hit return and Subversion will prompt for your username:

Authentication realm:  PLPA Subversion Access
Password for 'your_username':
Authentication realm:  PLPA Subversion Access
Username:

After you use the correct Subversion username and enter your Subversion password, the checkout will proceed.

NOTE: By default, Subversion caches your password under on your local computer (e.g., under $HOME/.subversion directory, or in your OS X keychain). Hence, you only need to enter it once. If you are uncomfortable with Subversion caching your password, consult the Subversion documentation.