From: Miguel A. Figueroa-V. <mi...@ie...> - 2009-03-13 16:23:50
|
On Fri, Mar 13, 2009 at 10:04 AM, Brad King wrote: > Miguel A. Figueroa-Villanueva wrote: >> Do we really need to release the website for each release of vxl? I >> would have thought that a next release of the website is a much >> improved one, not only a minor modification in a release link... > > I'm just preserving what is in CVS now. We don't have to do it for > future releases. ok >> Also, is there a way to restructure things without breaking it, so >> that the two 'vxl' in sequence are removed? It seems awkard to have >> three vxl on the url! >> >> http://vxl.svn.sourceforge.net/svnroot/vxl/vxl/trunk > > The first two are hard-coded by sourceforge (vxl.svn and svnroot/vxl). > The third one distinguishes the vxl project module from the www module: > > http://vxl.svn.sourceforge.net/svnroot/vxl/vxl/trunk > http://vxl.svn.sourceforge.net/svnroot/vxl/www/trunk > > This is the standard svn layout. We may also create a third 'dash' > module after the migration is done to put dashboard scripts and such. > > Actually, a normal checkout command will have 'vxl' four times: > > svn co http://vxl.svn.sourceforge.net/svnroot/vxl/vxl/trunk vxl > > so that the local working tree gets the name 'vxl'. I don't think this > matters though. Users will just cut-and-paste whatever our instructions > say. Well, this is what worried me... when I go to checkout something from sourceforge I tend to visit the cvs/svn page: for svn: http://sourceforge.net/scm/?type=svn&group_id=24293 for cvs: http://sourceforge.net/scm/?type=cvs&group_id=24293 The instructions for cvs apply, but the instructions for svn tend to suggest that one should use: svn co https://vxl.svn.sourceforge.net/svnroot/vxl/trunk vxl Of course, these are generic instructions, but it might generate some confusion... Then again, if a user is using subversion, he should probably be able to deal with this easily... or not. --Miguel |