Version Controling Modifications

Ruby Apps Typo
1

When running off Typo-Trunk what is the recommended way to store
modifications to core or theme within SVN? Normally one would use
SVN:Externals to link in some external libraries, such as vendor/rails,
but
how are people managing to run off trunk, and version control their
bug-fixes, theme changes, etc?

Thanks!

Josh

2

Josh K. wrote:

When running off Typo-Trunk what is the recommended way to store
modifications to core or theme within SVN? Normally one would use
SVN:Externals to link in some external libraries, such as vendor/rails,
but how are people managing to run off trunk, and version control their
bug-fixes, theme changes, etc?

There are two ways to do this.

  1. You can use vendor branches in subversion. More info from the svn
    book: Vendor branches

  2. Look at using svk http://svk.elixus.org/. This will let you take
    a copy of the typo trunk and carry on checking in your own changes as
    well. You’ll still be able to separate out the two.

I’ve just switched from vendor branches to svk and I really recommend it
http://happygiraffe.net/blog/archives/2006/07/30/typo-4-0ish. svk can
be a pain to install, as it has a lot of dependencies, but if you’re on
Debian or FreeBSD, it’s prepackaged anyway. But I did have real
troubles maintaining a vendor branch using svn.

-Dom

3

On 8/2/06, Josh K. [email protected] wrote:

When running off Typo-Trunk what is the recommended way to store
modifications to core or theme within SVN? Normally one would use
SVN:Externals to link in some external libraries, such as vendor/rails, but
how are people managing to run off trunk, and version control their
bug-fixes, theme changes, etc?

I don’t know about “recommended”, but I use Darcs and a script called
tailor that lets me synchronize with typo SVN. I am actually just
putting the finishing touches on a blog post describing my setup. Look
for it at http://fiatdev.com/ in the next day or so.

Also, you can use SVK to do the same thing. See
Distributed development with SVK :: scottstuff.net.
The SVK setup is probably a little simpler to get set up, but I think
that the Darcs method is more usable.

Phil

4

I’m using SVK. I have a mirror of typo trunk, then a local branch. I
treat the local branch as my SVN repository, and I deploy from there
via capistrano. All my extra files and junk are committed to that
local branch, which can be synced with my trunk mirror with one
command.

It feels a bit awkward, still, but it’s the only thing I could come up
with.

On 8/2/06, Josh K. [email protected] wrote:

Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list

–
Cheers,

Kevin

“Any sufficiently advanced technology is indistinguishable from
Magic.” - Arthur C. Clarke

5

On 8/2/06, Josh K. [email protected] wrote:

When running off Typo-Trunk what is the recommended way to store
modifications to core or theme within SVN? Normally one would use
SVN:Externals to link in some external libraries, such as vendor/rails, but
how are people managing to run off trunk, and version control their
bug-fixes, theme changes, etc?

Thanks for the quick responses! I’ve been meaning to check out SVK,
looks
like I have a good reason to now.

Josh