Hi
>The designers of the externals feature envisioned maybe a handful of
external library dependencies that don't vary much over time.
>These are automatically pulled into a working copy, much like an
automated svn checkout.
>But the design doesn't account for what happens when people start using
svn:externals for variant management or large-scale component reuse.
>If you're pulling together project components from externals in various
combinations, like lego blocks, or simply have many externals, don't use
the svn:externals properties as the primary source of your configuration
data.
Yes, currently I am pulling together project components from
externals... like lego blocks. I think in nearly all situations we are
referencing a specific revision of the external directory structure in
the project external properties. The vast majority of the time the
external data is actually within the same repository, but there are a
few situations where it is in another repo.
>Do it the other way: Store your component configuration in a versioned
file or even a database, and write a script to configure svn:externals
properties based on that data. Maybe even add an automated check into
the mix that makes sure the svn:externals in the repository's HEAD
revision >are in sync with your primary externals configuration source.
I think unfortunately this is where you lose me :) I am not too sure why
this is too different from "the other way". In both situations I end up
with a set of project folders with svn:externals on them..... but the
latter I say have one top level "externals.lst" and associated script
file that is used to apply them. Probably a reflection of my knowledge
level but not clear where the gain has come from ?
>Hope this helps,
>Stefan
********************************************************************
This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person.
MBDA UK Limited, a company registered in England and Wales, registration number 3144919 whose registered office is at Six Hills Way, Stevenage, Hertfordshire, SG1 2DA, England.
********************************************************************
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
Received on 2010-11-08 11:24:47 CET