Thanks to everyone who provided me with very helpful feedback re: my
problem of "software distribution with subversion". I am re-evaluating
the project, and how to complete it best.
Thanks!
Jason.
The OP isn't subscribed and so probably didn't see your reply.
Branko Čibej wrote on Fri, Feb 01, 2013 at 00:37:41 +0100:
> I expect you've considered this option, but just to add it to the list:
Guten Tag Jason Keltz,
am Donnerstag, 31. Januar 2013 um 23:10 schrieben Sie:
> Any ideas that anyone might be able to offer?
As it seems most answers vote against using Subversion and use rsync
or some alternative instead, I would like to add some ideas which vote
for Subversion because I use a
On Thu, Jan 31, 2013 at 8:18 PM, Jason Keltz wrote:
> >
> See my email to Les... If only the rsync server could save a copy of the
> file checksums when it runs, it would probably decrease the sync time by
> half and save a whole lot of disk activity...
If you don't use the --ignore-times option
On Thu, Jan 31, 2013 at 8:14 PM, Jason Keltz wrote:
>>
>> I'd think it is exactly the problem that rsync is intended to handle.
>
> rsync is great when you want to sync the contents from one machine to
> another machine in one direction.. (unison if you need dual direction
> sync...) I thoug
On Thu, Jan 31, 2013 at 9:18 PM, Jason Keltz wrote:
> On 31/01/2013 9:13 PM, Ryan Schmidt wrote:
>> Subversion is not a software distribution tool; it is a document and
>> revision management system. Use a different tool. As someone else said,
>> rsync seems like a good tool for this job; I didn'
On 31/01/2013 9:13 PM, Ryan Schmidt wrote:
On Jan 31, 2013, at 20:05, Jason Keltz wrote:
On 31/01/2013 6:06 PM, Bob Archer wrote:
What you need to do could work. I assume this "software" in order to run can
build built or whatever during your nightly update on each client?
You keep saying "r
On 31/01/2013 6:40 PM, Les Mikesell wrote:
On Thu, Jan 31, 2013 at 4:10 PM, Jason Keltz 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 a
On Jan 31, 2013, at 20:05, Jason Keltz wrote:
> On 31/01/2013 6:06 PM, Bob Archer wrote:
>>
>> What you need to do could work. I assume this "software" in order to run can
>> build built or whatever during your nightly update on each client?
>>
>> You keep saying "rsyncing" ... you wouldn't us
On 31/01/2013 6:06 PM, Bob Archer 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, softwa
On Thu, Jan 31, 2013 at 4:10 PM, Jason Keltz 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 reg
I expect you've considered this option, but just to add it to the list:
Why not use a package manager like apt or yum, or a distributed
configuration manager such as puppet, to manage your servers?
While Subversion can be used as a substitute, it's not really suited for
this kind of application --
> 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 th
Hi.
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 t
14 matches
Mail list logo
