Good procedures for vendor drops?

[Wesley Leggette <wl...@cleversafe.com>]

The Subversion Book [1] provides a good example of how to handle vendor 
code. Is this method common in the wild? Does anybody have any further 
suggestions?

I'm planning on handling third-party sources with two repos.

Third-Party Repo:

thirdparty/
    vendor/
       boost/
          current/
          1.32.0/
       bzip2/
          current/
          1.0.3/
       curl/
          current/
          7.15.4/
    branches/
    tags/
    trunk/
       build/   # a common build script lives here
          build-thirdparty.sh
       src/
          boost/
          bzip2/
          curl/

Project Repo:

client-server-project/
    build/
    client/    # client code lives here
    common/    # common code lives here
    configure
    configure.ac
    server/    # server code lives here

    thirdparty/   # <-- an svn:external to the third-party repo
       build/
          build-thirdparty.sh
       src/

    tools/     # other stuff


Does anybody have any suggestions for improvements?

There is a whole writeup on how I plan on doing this [2].


Thanks,
Wesley Leggette
Cleversafe, LLC



[1] 
http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.advanced.vendorbr
[2] http://wiki.cleversafe.org/Third-Party_Sources

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org