On 11.06.2010 22:36, Jean-Marc van Leerdam wrote:
> Over the years I have been using (T)SVN for lots of different
> projects, but this is something new. I want to start my own
> development (private repository) of some components/plugins for
> Joomla!. The folder structure of Joomla! is such that the files for
> these components/plugins must be spread across the source tree of
> Joomla! itself.
> So, on the one hand I have a need for a working copy (develop/test
> setup) that contains the Joomla! source as an svn:external, but that
> has regular folders/files for my personal additions.
> Are there some other (T)SVN users with experience who could give some
> hints on how to proceed?
> Is is best to create a separate WC and add some 'build' step to copy
> the code into the Joomla! WC (or export) prior to testing (a bit of a
> PITA compared to just saving the files and hitting f5 in the browser).
In TSVN, I use the build scripts to patch or otherwise modify external
sources if needed.
If you have a good build script, you could do it like this (having the
Joomla! sources included with svn:externals, meaning they're versioned):
* update the wc
* modify files in external sources as required
* copy files from another versioned folder to the externals folders
* build everything
* do post-build steps like uploading files, ...
* run 'svn revert' on the modified but versioned files so they don't
mess up the overlays all the time
You can check out the TSVN build scripts to see how we do it: in our
'ext\build' folder, some of those scripts patch external sources by
copying our modified versions over to the original location of those
sources. Our modified versions of those files are also kept in the
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-06-13 15:59:33 CEST