(ok, so i'm not certain this is the right list ... but server mgmt seems to be
closest topic ... pls let me know if this is better posted elsewhere. thx.)
as many do, i have a relatively heavily customized /usr/local/ tree that i
build into on my local (desktop) OSX 10.3.9 G4 box.
i've now also got a number of other boxes (G3s, G4s, both 'native' and
cpu-upgraded) that, eventually (will/should), get the same tools/widgets built
into their /usr/local/ trees.
typically, i end up building all on each box ... til now, a set of scripts has
mostly minimized the effort ... but as those trees grow, its getting to be a
hassle.
i should, rather, build once and sync/deploy ...
fwiw, more often than not, i do NOT build statically, and need 'all' my
dependencies (libs, incs, etc) on each box.
###########
## question:
#
short of pkg'ing and installing each build, what's the 'recommended' way to
build once & sync?
to my understanding, options include:
(a) building a SVN repo from the local /usr/local dir and co'ing onto each box
(b) using rsync, CopyCloner, Synchronize!Pro, etc. to synch dir contents
(c) use UofM's Radmind client/server file admin app
(d) mount the filesys' and simply ditto or cp ...
i *am* assuming that, as long as i'm using same OS, build tools and app
versions, and building for a common 10.3 target, that i'm *not* going to be
sensitive to 'box differences' ... correct?
