(Replaced content with "{{header|infra}} This SOP has moved to the fedora Infrastructure SOP git repo. Please see the current document at: http://infrastructure.fedoraproject.org/infra/docs/fedorah...")

(19 intermediate revisions by 9 users not shown)

Line 1:

Line 1:

{{header|infra}}

{{header|infra}}

−

= Setup a New Mercurial, GIT, Bazaar, or SVN Repository =

+

This SOP has moved to the fedora Infrastructure SOP git repo. Please see the current document at: http://infrastructure.fedoraproject.org/infra/docs/fedorahosted-repo-setup.txt

−

Since Fedora already has public git and mercurial servers it's pretty easy to add a new project to them.

+

For changes, questions or comments, please contact anyone in the Fedora Infrastructure team.

−

−

== Mercurial Repository ==

−

You'll need to know three things in order to start the mercurial repository.

−

# PROJECTNAME -- what the project wants to be called.

−

# OLDURL -- how to access the project's current sourcecode in their mercurial repository.

−

# PROJECTGROUP -- the group setup in the account system for readwrite access to the repository.

−

−

The Mercurial repository lives on the hosted server. Access it by logging into hosted1 Then follow these steps:

The Mercurial [http://www.selenic.com/mercurial/wiki/index.cgi/NotifyExtension Notify extension] can be used to send out email when commits are pushed to a Mecurial repository. To enable notifications, create the file ''/hg/$PROJECTNAME/.hg/hgrc'':

−

−

<pre>

−

[extensions]

−

hgext.notify =

−

−

[hooks]

−

changegroup.notify = python:hgext.notify.hook

−

−

[email]

−

from = admin@fedoraproject.org

−

−

[smtp]

−

host = localhost

−

−

[web]

−

baseurl = http://hg.fedoraproject.org/hg

−

−

[notify]

−

sources = serve push pull bundle

−

test = False

−

config = /hg/$PROJECTNAME/.hg/subscriptions

−

maxdiff = -1

−

</pre>

−

−

And the file ''/hg/$PROJECTNAME/.hg/subscriptions'':

−

<pre>

−

[usersubs]

−

−

user@host = *

−

−

[reposubs]

−

</pre>

−

−

== Git Repository ==

−

You'll need to know three things in order to start the git repository.

−

# PROJECTNAME -- what the project wants to be called.

−

# OLDURL -- how to access the project's current source code in their git repository.

−

# PROJECTGROUP -- the group setup in the account system for write access to the repository.

If you don't have any files in the repository then git will balk about it. Do this on hosted1 to make your repo work:

−

−

<pre>

−

$ cd

−

$ git clone /git/$PROJECTNAME.git

−

$ cd $PROJECTNAME

−

$ touch file

−

$ git add file

−

$ git commit

−

$ git push /git/$PROJECTNAME.git/ master

−

</pre>

−

−

This should setup all the files needed for the repository.

−

−

=== Commit Mail ===

−

If they want commit mail, then there are a couple of additional steps.

−

<pre>

−

$ echo $COMMITLIST > commit-list

−

$ echo $DESCRIPTION > description

−

$ ln -s /usr/bin/fedora-git-commit-mail-hook hooks/update

−

</pre>

−

−

== Bazaar Repository ==

−

You'll need to know three things in order to start a bazaar repository.

−

# PROJECTNAME -- what the project wants to be called.

−

# OLDBRANCHURL -- how to access the project's current sourcecode in their previous bazaar repository. Note that a project may have multiple branches that they want to import. Each branch will have a separate URL. (The project can import the new branches after the repository is created if they want.)

−

# PROJECTGROUP -- the group setup in the account system for readwrite access to the repository.

−

−

The bzr repository lives on the hosted server. Access it by logging into hosted1 then follow these steps:

−

−

The first stage is to create the Bazaar repository.

−

<pre>

−

$ cd /srv/bzr/

−

$ # This creates a Bazaar repository which has shared storage between branches