On May 19, 2006, at 2:31 PM, Ben Bleything wrote:
On Fri, May 19, 2006, Jeremy Kemper wrote:
I'm using svn:externals for shared models with no trouble (yet.)
What sort of nasty crap have I unwittingly invited?
I had a pair of applications that shared some of their models but not
all. I needed to share those models that were common but be able to
have some models that were specific to each application. I couldn't
figure out a clean way to do that.
I'd love to hear a suggestion, though. I didn't try very hard.
The simplest is to share them all-- surprisingly not-so-bad, though I
had some knee-jerk dislike.
Another is to namespace your models with modules+subdirs and cherry-
pick dirs for svn:externals as you please. This requires a bit of
work changing Foo to SomeModule::Foo but tickles the "it feels right"
spot by keeping a large models dir comprehensible and by sharing
'chunks' only as needed.
Since replying, I did come up with a couple of externals annoyances:
1. svk doesn't deal with them at all
2. they're dumb urls, so your branch from trunk to branches/some-
dev-feature leaves your externals pointing to the other app's trunk.
(I haven't tried Engines for this task so I can't say how they compare.)
jeremy
_______________________________________________
PDXRuby mailing list
[email protected]
IRC: #pdx.rb on irc.freenode.net
http://lists.pdxruby.org/mailman/listinfo/pdxruby
