On 2007-11-07 Fabio Fullin wrote:
> I'm using subversion for several projects
> I install the final binaries to the clientes
(I assume you mean the 'svn' binaries.)
This may not be the best approach. An alternative is to have all
clients mount/map a shared drive which holds the 'svn' client
binary(ies). You might have to have platform-specific areas on
the shared drive, and some environmental setup reflecting the
platform stuff. But all in all this is usually the easiest way
to keep client environments up to date (without actually having
to touch the clients). When you're needing to do the 'svn'
version update, you only have to update the share-server (maybe
once for each platform), and all the clients automatically see
the updated version.
> Is there a way the same program or a different product checks
> in a web site the last revision and updates the package?
That's another possibility, but it depends on the diversity of
your client platforms. Each platform has its own method. On
Linux, you can leverage apt/yum/up2date/etc; on Mac I think it's
"ports" or something; and I have no clue on Windows. Probably
all of them have a way to at least keep up with patches. To do
major updates you'll need to find some third-party
(b)leading-edge "depot" or do an actual "distribution upgrade" as
they become available in "package" form.
You could also standardize on some "push" installation
methodology and script your way into keeping everything up to
(I'm realizing now it's not too clear exactly what you are
actually asking. I suppose you could use subversion itself to
host/update some binary on client machines. It's usually not
considered a best practice to be storing your binaries in the
I prefer the first (shared) approach for any sizeable user bases.
_ _ ___
|V|icah |- lliott
" " """
mde_at_MicahElliott.com <>< http://MicahElliott.com
PGP: 0x7C07CBF0 ICQ: 369060435 Linux/Ubuntu: 417195/12440
Received on Thu Nov 8 04:10:32 2007