Using the Lazarus-ccr SVN repository

From Free Pascal wiki
Jump to: navigation, search

This page describes the policy for using the Lazarus Code and Component Repository on SourceForge (Lazarus CCR project). Anybody porting components to Lazarus can ask the Lazarus CCR project admin for write access. The Lazarus CCR Project has both SubVersion and Git repositories.

Contents

Read access

Everybody has read access to this SubVersion and Git repositories. You can browse the SubVersion repository at http://lazarus-ccr.svn.sourceforge.net/viewvc/lazarus-ccr/ or the Git repositories at http://sourceforge.net/p/lazarus-ccr/_list/git

For more information about the contents of the CCR, please see Components and Code examples

Write access

Unfortunately, at this moment Sourceforge doesn't support restricting access to SVN to only a subtree of the complete repository. So we will give write access to the complete SVN tree, with the assumption that SVN committers will only write to their own part of the tree.

Please contact the admins about Git write access too.

If you want to commit something to a part of the tree for which you are not the maintainer, please contact the maintainer before committing.

SubVersion

Working with the Lazarus-CCR SVN repository

This is a short guide mainly focusing on the URLs and sourceforge specifics. It is not an introduction to the use of SVN.

Checking out

The Lazarus-CCR is located at https://svn.code.sf.net/p/lazarus-ccr/svn

The following command will check out the complete tree into the lazarus-ccr subdirectory of your current directory:

svn co https://svn.code.sf.net/p/lazarus-ccr/svn lazarus-ccr
Committing

The first time you commit something, svn will ask for your password. Use the password, which belongs to your SourceForge account. This password is stored in the svn metadata in the checked out tree and won't be asked the next time.

Directory owners

The following lists shows the directory structure and their maintainers.

Git

It the Git area of Lazarus CCR you can have one repository for every project. Thus making read/write access much easier to manage.

Repository owners

Personal tools