hi all.
to lighten my growing frustration with CVS i would like to propose again to switch the Gem development from CVS to SVN.
the main reason for me right now is, that my personal online-time has been greatly reduced within the last weeks (and it is not clear whether it will grow again); with CVS i unfortunately need to be online for quite everything (even to query whether i have modified any files), this is better with SVN (at the expense of harddiskspace)
other boni: - the main Pd-repository is now using subversion too - all the fancy stuff about renaming files, fixing execution-bits, deleting unused directories and so on - standardized format for links to the current (or a certain) development branch; the main-branch could be https://pd-gem.svn.sourceforge.net/svnroot/pd-gem/Gem/trunk; what would it be on CVS? cvs://cvs.gem.iem.at/cvsroot/pd-gem/Gem ? (it's probably readable by humans, but not standardized and thus not readable by machines) - some of the remaining GemLibs (e.g. FTGL) are now also hosted in svn-repositories upstream, so we could more easily include them.
i would suggest to keep the repository at sourceforge (why bother with setting up our own)
plllleazzzze!!
fgam,sdr IOhannes
This sounds like a good idea to me.
Are there any reasons people would like to stick with CVS? (IDE integration perhaps?)
Bring on SVN.
.b.
IOhannes m zmoelnig wrote:
hi all.
to lighten my growing frustration with CVS i would like to propose again to switch the Gem development from CVS to SVN.
the main reason for me right now is, that my personal online-time has been greatly reduced within the last weeks (and it is not clear whether it will grow again); with CVS i unfortunately need to be online for quite everything (even to query whether i have modified any files), this is better with SVN (at the expense of harddiskspace)
other boni:
- the main Pd-repository is now using subversion too
- all the fancy stuff about renaming files, fixing execution-bits,
deleting unused directories and so on
- standardized format for links to the current (or a certain)
development branch; the main-branch could be https://pd-gem.svn.sourceforge.net/svnroot/pd-gem/Gem/trunk; what would it be on CVS? cvs://cvs.gem.iem.at/cvsroot/pd-gem/Gem ? (it's probably readable by humans, but not standardized and thus not readable by machines)
- some of the remaining GemLibs (e.g. FTGL) are now also hosted in
svn-repositories upstream, so we could more easily include them.
i would suggest to keep the repository at sourceforge (why bother with setting up our own)
plllleazzzze!!
fgam,sdr IOhannes
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
hi all.
B. Bogart wrote:
This sounds like a good idea to me.
thanks for the feedback.
Are there any reasons people would like to stick with CVS? (IDE integration perhaps?)
it seems like nobody has objections (hopefully everybody has had the possibilities to read my suggestions by now...)
as with IDE-integration: at least for VisualStudio the only free (as in beer) version-control integration i was able to find was AnkhSVN; for xcode there should be plugins for both cvs and svn.
so i will now start the migration process: #1 make CVS-repository read-only #2 migrate CVS-repository to SVN #3 announce the SVN-repository
fmgasd.r IOhannes
IOhannes m zmoelnig wrote:
so i will now start the migration process: #1 make CVS-repository read-only #2 migrate CVS-repository to SVN #3 announce the SVN-repository
due to sourceforge's quality of services it took a bit longer than expected. (it wasn't _that_ bad though; i just forgot to inform you as soon as it was up and running)
the repository of Gem has switched from CVS to subversion; the main development line is now available at https://pd-gem.svn.sourceforge.net/svnroot/pd-gem/trunk/Gem/
joyous day
gfmasdr IOhannes
On Jul 23, 2008, at 2:58 AM, IOhannes m zmoelnig wrote:
IOhannes m zmoelnig wrote:
so i will now start the migration process: #1 make CVS-repository read-only #2 migrate CVS-repository to SVN #3 announce the SVN-repository
due to sourceforge's quality of services it took a bit longer than expected. (it wasn't _that_ bad though; i just forgot to inform you as soon as it was up and running)
the repository of Gem has switched from CVS to subversion; the main development line is now available at https://pd-gem.svn.sourceforge.net/svnroot/pd-gem/trunk/Gem/
joyous day
Yeeee haw! Congrats. I suppose that means I need to update the auto- builds to point to SVN now...
.hc
gfmasdr IOhannes
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
------------------------------------------------------------------------ ----