Yeah, the svn:external property is set for the directory, and the directory is version controlled just like any other file. Its definitely nifty. If you've ever used perforce, its sort of like creating a client that everyone can sync to, and that is version controlled.
A good use of it for your projects is shared libraries. For example, if you have lib1, lib2, and lib3, you can create a project1 folder that has lib1, lib2, and lib3 as svn:externals, and create a project2 folder that has the same svn:externals. You can checkout both projects, and your working environment is all set. So to do what I propose, all I need to do is have my own svn server in which it will only contains one folder in the repository called something like OSG_OT_3rdParty. I think many osg-developers will be doing this anyways. At least ones that develop on windows. I suspect there are more developers on Linux than on Windows because it is such a pain to get all the files in place on Windows. But, as we know there are more Windows users of osg than Linux. I just wish we could harness them in to the osg dog sled. Zach -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joakim Simonsson Sent: Monday, February 19, 2007 17:16 To: osg users Subject: Re: [osg-users] svn simplification I wasn't aware of that it is was version controlled. According to Jan's mail: It is possible to omit the externals when you are checking out something with the svn:external property set. The svn:external property doesn't allow you to choose the destination directory of the externals, does it? In ouy case we want the .. directory of osg, so OpenThreads and OpenSceneGraph can reside in the same directory. On Mon, 19 Feb 2007 23:08:31 +0100, Zach Deedler <[EMAIL PROTECTED]> wrote: > Hi Joakim, > > That is pretty much what svn:externals does. It is just a script that > pulls in different locations of libraries. It is also version > controlled. The advantage of the svn:externals is that it will run on > all platforms where as scripts need to be modified per platform. > > Zach > >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of Joakim >> Simonsson >> Sent: Monday, February 19, 2007 16:41 >> To: osg users >> Subject: Re: [osg-users] svn simplification >> >> >> IMHO a better alternative to the limited external property is to have >> a script that checks out dependencies. The script is optional to run, >> so if you don't want/need any external dependencies, you simply don't >> run the script. The script could check out any version of the >> dependencies. >> >> The most powerfull advantage, is that the script itself is version >> controlled!!!! This means that if you check out an older version of >> openscenegraph, you'll get the correct version of all the >> dependencies, that was current at that time. >> >> On Mon, 19 Feb 2007 21:52:05 +0100, Jan Ciger <[EMAIL PROTECTED]> >> wrote: >> >> > 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? >> > >> >> 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. >> > >> > 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. >> > >> > Let people think for themselves, they are not babies :) >> > >> > Jan >> > >> > >> >> >> >> -- >> Joakim Simonsson >> _______________________________________________ >> osg-users mailing list >> [email protected] >> http://openscenegraph.net/mailman/listinfo/osg-users >> http://www.openscenegraph.org/ >> > > _______________________________________________ > osg-users mailing list > [email protected] > http://openscenegraph.net/mailman/listinfo/osg-users > http://www.openscenegraph.org/ -- Joakim Simonsson _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/ _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
