Hans-Christoph Steiner wrote:
On Dec 3, 2008, at 6:19 PM, Chris McCormick wrote:
I don't know about svn --ignore-externals, anyone care to expand on
that? (yes, I can RTFM, but I am talking real world experience as
related to Pd, which TFM will not tell me)
hmm, "--ignore-externals" ignores external-references when doing a checkout/update.
probably a small real-world example can illustrate the use of "--ignore-externals".
one of the projects i am involved in, is the CUBEmixer, basically a big Pd-application. it depends on a few externals, hosted in the pure-data repository.
if you run % svn checkout https://svn.sourceforge.net/svnroot/iem/spatialization/CUBEmixer/trunk/src/l... you will get this directories (1st level): libs/ libs/popup libs/folder_list libs/hdspm_mixer libs/aconnect libs/hcs libs/iem_ambi libs/iem_bin_ambi libs/iemgui libs/iem_spec2 libs/iemlib libs/iemmatrix libs/miXed libs/osc libs/net libs/zexy
however, if you don't care for all the external references, you could do instead: % svn checkout --ignore-externals https://svn.sourceforge.net/svnroot/iem/spatialization/CUBEmixer/trunk/src/l... you will only get: libs/ libs/popup libs/folder_list
so when using the "--ignore-externals" you can checkout a repository as if there were no svn:external properties set in this repo.
What about the idea of
having a separate section like /pure-data/svn-externals? If people
object to having the imported releases in trunk, I can easily manage
that in the pd-extended branch.
to reiterate: i believe that nobody objects to having releases imported. the problem is that people do not make releases that could be imported.
and whatever you can easily manage, has to be managed by you; i don't want to add another piece of work to your heap.
mfga.r IOhannes