On Thu, Jan 31, 2013 at 4:10 PM, Jason Keltz <jas_at_cse.yorku.ca> wrote:
>
> I am faced with a problem where I need to distribute a directory containing
> about 60 GB worth of software on a Linux file server to about 100 systems.
> The software must be localized on those systems and not shared out over NFS.
> On a regular basis, software may be added or removed from the directory, and
> all the clients should update accordingly in the evening. During the update
> period, some client systems may be off.
>
> I think that Subversion would be a reasonable way to solve this problem
> which isn't quite the type of problem that rsync is intended to handle
> (because of the number of machines).
I'd think it is exactly the problem that rsync is intended to handle.
> However, for a variety of reasons, I
> don't want to run subversion on the actual file server. Instead, nightly,
> I'd like to rsync changes in the contents of the software directory on the
> file server to a software distribution server which would run its own
> svnserve. The clients would then connect up to the server nightly, and
> update themselves accordingly. Because of the versioning, if a client
> misses an update, it would be updated the next time around, even if its been
> off for a while.
Subversion would give you the option of intentionally maintaining your
targets at different revision levels, but at a cost of needing a
'working copy' format where you have an unneeded 'pristine' duplicate
copy of everything.
> However, after the rsync happens, I now need to run a
> command that would update the repository with the state of the working
> directory. However, it's not exactly clear how this would work? Running an
> "svn update" isn't going to delete directories from the repository that were
> deleted from the working directory.
Sure it will - it will make it match the state of whatever version you
are updating to.
> I believe you need to use "svn delete"
> for this?
That is for when you are making the changes you intend to commit.
--
Les Mikesell
lesmikesell_at_gmail.com
Received on 2013-02-01 00:40:37 CET