Re: Hosting Arch archive on Sourceforge

Hi,

I've been playing around with the archive hosted on sourceforge and there=
 =20
doesn't seem to be too many problems with using it. The most important =20
thing to remember is to either change your umask or do a chmod after =20
commiting to make sure other group members still have write access.

I have now created a new archive ([email protected]) which ha=
s =20
been branched off the sourceforge archive ([email protected]) =20
instead of Kristian's. This is located at

http://www-users.york.ac.uk/~djh123/arch2005/

and contains the two branchs zinf--browsermm and zinf--xmltree.

Would anyone have any objections to moving the [email protected]=
 =20
archive from /home/groups/z/zi/zinf/archive to =20
/home/groups/z/zi/zinf/htdocs/archive so that it is avaliable via the =20
website? It seems kind of stupid to have keep it private. If you start =20
using it, and it gets moved, it can simply be reregistered at the new =20
location without breaking anything.

I have written some very very simple shell scripts to illustrate some =20
examples of how to use the archive for commiting to CVS.
First off you need to register the archive, and create a cvs-arch hybrid =
=20
tree for tla-cvs-sync to run in.


#!/bin/sh
#Registers the Zinf archive and creates a CVS/Arch Hybrid tree
#Usage:
#	zinf-cvs-setup <sourceforge username> <hybrid dir name>
#e.g.
#	zinf-cvs-setup turtledavid zinf-hybrid

#Register archive
tla register-archive =20
sftp://[email protected]/home/groups/z/zi/zinf/archive

#Check out most recent cvs-trunk
tla get [email protected]/zinf--cvstrunk $2

#Check out from CVS
cvs -z3 -d:ext:[email protected]:/cvsroot/zinf co -P zinf

#Make hybrid tree
cp -rf zinf/* $2
cp -f zinf/.* $2
rm -rf zinf


Then to commit to CVS, the branch you want to commit needs to be merged =20
into the cvstrunk branch, and then tla-cvs-sync needs to be run

#!/bin/sh
#Merges a branch into CVS
#Usage:
#	zinf-cvs-merge <log summary> <branch name>
#e.g.
#	zinf-cvs-merge "Update BrowserMM" =20
[email protected]/zinf--browsermm--0.5

TEMP_MERGE_DIR=3Dzinf-merge
HYBRID_DIR=3D~/src/zinf/zinf-hybrid
SF_USERNAME=3Dturtledavid

#Merge branch into cvstrunk
tla get [email protected]/zinf--cvstrunk $TEMP_MERGE_DIR
tla star-merge -d $TEMP_MERGE_DIR $2
tla commit -d $TEMP_MERGE_DIR -s $1
rm -rf $TEMP_MERGE_DIR

#Sync With CVS
cd $HYBRID_DIR
tla-cvs-sync
ssh [email protected] "chmod -Rq ug+w =20
/home/groups/z/zi/zinf/archive"

Obviously, there is a problem with the above script in that it does not =20
check for errors as it happily commits away. So I highly recommend that =20
you either write a better shell script, or do each step manually. This is=
 =20
more of an example of how to do it.

The script always executes a chmod after commiting to CVS to make sure =20
other people can still commit to the archive. Please always remember to d=
o =20
this.

Using the above instructions I have now synced my browsermm branch with =20
CVS again, the two major highlights of which being
- MusicBrowserMM can now be run as the primary UI! (e.g. zinf -ui =20
musicbrowsermm)
- It no longer depends on any version of libglademm. (I've converted the =
=20
few glademm dialogs to gtkmm code)


Cheers,
David
--=20
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick