Chapter 7 of the subversion book talks about externals, which I think do just what we want for third party code, binaries, cross-platform tools, all of it. The difference between externals and branching the vendor tree seems to be... use externals if versions of the 3rd party stuff won't change much or won't change in a complicated way.
We can set an svn:externals property on any directory that we're going to use as LPS_HOME. We would write our scripts as if everything we need to do everything lives in a subdir of $LPS_HOME. Then svn update handles the mapping. As you say, self-contained build environments, but with less branch management. http://svnbook.red-bean.com/en/1.1/ch07s04.html On Apr 16, 2006, at 5:39 PM, Jim Grandy wrote: > ...and more trouble. I tried this on a branch in subversion, and > ran into more problems. The ant rules look ok -- they are not > linked to VENDOR_ROOT and all is well there. However, there are > four XSLT template files with relative paths from the source dir > back into the tools dir. Lines like this: > > <xsl:import href="../../../../tools/docbook-xsl-1.65.1/html/ > chunk.xsl"/> > > One option would be to revive that idea we discussed to branch the > vendor files into the source tree, so we'd have specific files and > subdirectories branched from /vendor into /openlaszlo/trunk/vendor > (and also into the branches and tags). > > Another avenue would be to figure out how to pass VENDOR_ROOT in to > the XSLT templates as parameters. I googled that a bit, and it > looks possible, but I'm beginning to wonder now whether we wouldn't > be better off with self-contained build environments. > > (For the benefit of laszlo-dev, these changes are to make > OpenLaszlo build in the new subversion repository. We have the > following structure now: > > /openlaszlo/trunk > /openlaszlo/branches/... > /tools > /vendor > > Where /vendor has external tools and code libraries, and /tools has > cross-project scripts and tools. The subversion book recommends > branching from /vendor into project source trees, and I'm starting > to think this is the right approach for us too.) > > > On Apr 16, 2006, at 3:45 PM, Jim Grandy wrote: > >> Hold on reviewing this. I think it should be VENDOR_ROOT, not >> TOOLS_ROOT, that we should be defining. I'll resubmit. >> >> On Apr 16, 2006, at 2:53 PM, Jim Grandy wrote: >> >>> Change 41553 by [EMAIL PROTECTED] on 2006/04/16 14:48:34 *pending* >>> >>> Summary:Doc build shouldn't depend on tools dir being a sibling >>> of LPS_HOME. >>> >>> Bugs Fixed:LPP-1970 >>> >>> Technical Reviewer: ben (pending) >>> QA Reviewer: jsundman (pending) >>> Doc Reviewer: n/a >>> >>> Details:Declare TOOLS_ROOT in build-op.xml. For now, substitute >>> ${LPS_HOME}/.. as default value if TOOLS_ROOT is not defined. When >>> we convert to subversion, this default value should be removed and >>> an error signaled if TOOLS_ROOT is not declared in the shell >>> environment. >>> >>> Tests:Ran 'ant doc' successfully. >>> >>> Affected files ... >>> >>> ... //depot/lps-dev/build-tools/build-opt.xml#3 edit >>> ... //depot/lps-dev/docs/src/build-dbk.xml#2 edit >>> ... //depot/lps-dev/docs/src/build.xml#9 edit >>> >>> >>> <changeset-41553.zip> >>> _______________________________________________ >>> Laszlo-dev mailing list >>> [email protected] >>> http://www.openlaszlo.org/mailman/listinfo/laszlo-dev >> > benjamin shine software engineer [EMAIL PROTECTED] _______________________________________________ Laszlo-dev mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
