Re: Hosting Arch archive on Sourceforge

Hi david,

   Strangely, I was playing around today with such an archive.
Please move the archive under htdocs.  How about under
htdocs/arch which I as trying out.

  


On Mon, 2005-02-07 at 23:41 +0000, David Hough wrote:
> Hi,
> 
> I've been playing around with the archive hosted on sourceforge and there  
> doesn't seem to be too many problems with using it. The most important  
> thing to remember is to either change your umask or do a chmod after  
> commiting to make sure other group members still have write access.
> 
> I have now created a new archive ([email protected]) which has  
> been branched off the sourceforge archive ([email protected])  
> 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]  
> archive from /home/groups/z/zi/zinf/archive to  
> /home/groups/z/zi/zinf/htdocs/archive so that it is avaliable via the  
> website? It seems kind of stupid to have keep it private. If you start  
> using it, and it gets moved, it can simply be reregistered at the new  
> location without breaking anything.
> 
> I have written some very very simple shell scripts to illustrate some  
> 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  
> 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  
> 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  
> 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"  
> [email protected]/zinf--browsermm--0.5
> 
> TEMP_MERGE_DIR=zinf-merge
> HYBRID_DIR=~/src/zinf/zinf-hybrid
> SF_USERNAME=turtledavid
> 
> #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  
> /home/groups/z/zi/zinf/archive"
> 
> Obviously, there is a problem with the above script in that it does not  
> check for errors as it happily commits away. So I highly recommend that  
> you either write a better shell script, or do each step manually. This is  
> more of an example of how to do it.
> 
> The script always executes a chmod after commiting to CVS to make sure  
> other people can still commit to the archive. Please always remember to do  
> this.
> 
> Using the above instructions I have now synced my browsermm branch with  
> CVS again, the two major highlights of which being
> - MusicBrowserMM can now be run as the primary UI! (e.g. zinf -ui  
> musicbrowsermm)
> - It no longer depends on any version of libglademm. (I've converted the  
> few glademm dialogs to gtkmm code)
> 
> 
> Cheers,
> David



-------------------------------------------------------
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=6595&alloc_id=14396&op=click