MG-GIMP
Artifact Content
Not logged in

Artifact 6b0fad119f6c6c298b0776a83aabe2ed330e4368:

Wiki page [cloning] by saul 2014-01-11 15:33:04.
D 2014-01-11T15:33:04.201
L cloning
P f289463119dc9fa23fd153fecff31505c582c6e6
U saul
W 2512
This MG-GIMP plug-in is currently being maintained using [http://www.fossil-scm.org/index.html/doc/trunk/www/index.wiki|Fossil] source code manager. You can clone this repository, thus gaining direct access to all of the files in the plug-in (including the history of their development) using the following command:

<pre>    fossil clone http://anonymous@chiselapp.com/user/saulgoode/repository/mg-gimp/ <i>mg-gimp.fossil</i></pre>

When prompted for a password, just hit RETURN. This will create a file named 'mg-gimp.fossil' in the current directory on your disk (you can name it something else if you wish, but I recommend that you use the <i>.fossil</i> extension). 

You can browse your cloned repo by issuing the following command:

<pre>    fossil ui <i>mg-gimp.fossil</i></pre>

This will open the repository in your webbrowser and present you with a user interface identical to the one you are viewing now, except that it will be your local copy and you will have the ability to change things as much as you like.

To actually access the scripts in the Fossil repo, create a directory to hold the scripts, change to that directory, and then run "fossil open <i>/path/to/mg-gimp.fossil</i>".

<pre>    mkdir <i>work</i>
    cd <i>work</i>
    fossil open ../<i>mg-gimp.fossil</i></pre>

The directory will be populated with the latest versions of the files in the trunk branch of the repo. My MG-GIMP repository is organized such that it can be opened in the top-level mediagoblin directory and the files will populate the Mediagoblin instance in their appropriate location. (It also adds a hidden file named ".fslckout" but this should not hinder your Mediagoblin deployment, and it is removed when you close the Fossil checkout).

The main branch of the repository is called 'trunk'. You can switch to a different branch by doing a "checkout" on it. For example:

<pre>    fossil checkout testing</pre>

After doing a checkout, only the files in the new branch will populate the directory. You can get a list of all of the branches in the repository with:

<pre>   fossil branch list</pre>

<h2>Exporting To GIT</h2>

You can export the MG-GIMP Fossil repository to GIT with the following steps:

<pre>  git init <i>new-git-repo</i>
  cd <i>new-git-repo</i>
  fossil export --git /path/to/<i>mg-gimp.fossil</i> | git fast-import</pre>

Of course, only the code files and their history are exported; GIT does not have any equivalent to the Fossil Wiki or Ticketing. 
Z c4cd74b40567083ce6a5caefc78a0f88