On Monday 19 February 2007, Zach Deedler wrote: > 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.
My point is not to teach somebody how to use subversion. My point is that if you do not know how to check out the code to need this sort of help for two modules, well, then you have much larger problems and you are probably not supposed to use the code in there - you may not be able to get it to work. Sometimes these types of "barriers" are useful to prevent you from harming yourself if you do not have enough knowledge/skills. > > 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. Nope. Delta3D is not only re-packaged OSG with dependencies. It is a whole game engine building on top of OSG. Big difference. > If your software is dependent on 3rd party software you have a > responsibility to maintain the final product. Sorry, no. As an author of the code I cannot be made responsible to maintain whatever breakage others do in their code. I can only update my code to work with a known-good version. > 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. This is true if-and-only-if the 3rd party code is under Subversion control. Which is not the case for most of the OSG dependencies. So the whole point is moot. > 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. I am not sure what you mean. > 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). Still, it makes no sense if the 3rd party libraries are not in Subversion. The script idea proposed by Joakim is at least going to work. Jan -- Jan Ciger GPG public key: http://www.keyserver.net/
pgpOrliDM40IE.pgp
Description: PGP signature
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
