Hi Jan, Comments posted below
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jan Ciger > Sent: Monday, February 19, 2007 15:52 > To: osg users > Subject: Re: [osg-users] svn simplification > > On Monday 19 February 2007, Zach Deedler wrote: > > Hello, > > > > RECOMMENDATION > > I highly recommend doing this for OpenSceneGraph and OpenThreads. > > Otherwise, novices of svn will definitely screw something up. > > Sorry, I do not agree. If you are novice, you are NOT > supposed to use the bleeding edge code in the repository > anyway. And if you are unable to follow the instructions for > checking out the code, are you sure you will be able to build it? Everyone is a novice of svn at some point, so I don't believe that is a valid argument. I believe this would simplify the instructions for osg-users and bring in more developers. The only argument I can see against this is that you have an extra directory. > > > We could also create a trunk that externally references > 3rdParty libs > > (if they are in svn) such as ReplicantBody, Cal3D, dem, > etc, but that > > will probably be too overwelming for some. > > Really bad idea - most of these projects do not use SVN but > CVS or sometimes only snapshots are available. Not to mention > that the CVS code for 3rd party libs is by far not the most > stable and you usually do not want/need it. I don't think this should be part of OSG's main trunk. It'd just be nice to give users easier access to all tools. I suppose this is why sites like Delta3D spawn. > > Moreover, who is going to maintain it? You will get only a > bunch of errors, making things even worse whenever some 3rd > party developer changes their repository structure. Moreover, > Linux developers get many of these libs on their systems by > default, I definitely do not want to check out many megabytes > of stuff just to get two libraries I need. If your software is dependent on 3rd party software you have a responsibility to maintain the final product. Currently, if a 3rd party developer changes their repository structure, you have to change your download/build instructions. Using svn:externals allows your instructions to not change. You can specify svn:externals to be specific revisions or branches. This is much more efficient than maintaining instructions that can be different for multiple platforms. Besides, if maintaining 3rd Party software becomes too cumbersome, the maintainer can choose to move away from using it. I believe this is being experienced now. Also, I'm not suggesting using svn:externals of development branches of the 3rd Party software. I'm suggesting using releases. Ah well, it looks like there is only 1 dependent library now instead of 2. (OT/OP). > > Let people think for themselves, they are not babies :) > > Jan > > > -- > > Jan Ciger > GPG public key: http://www.keyserver.net/ > > _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
