Distributing applications

Jaime Wyant programmer.py at gmail.com
Wed Mar 2 22:22:15 CET 2005


Sneaky!  I like it.  Now if there was only a subversion python module...

jw

On Wed, 02 Mar 2005 22:08:45 +0100, Thomas Heller <theller at python.net> wrote:
> "Serge Orlov" <Serge.Orlov at gmail.com> writes:
> 
> > Jaime Wyant wrote:
> >
> >> This becomes especially hairy when someone is updating from 1.0 to
> >> say 1.5.  Then I have to keep track of all the deltas between
> >> 1.0/1.5. My way is much simpler because I don't have to keep up with
> >> *anything*. As long as I test my code against my custom built
> >> distribution, it ought to JUST WORK.
> >>
> >> I don't trust myself to keep up with anything ;).
> >
> > Now I follow you :) I agree that updating py2exe apps requires package
> > management utilities. I don't think they will be messy, it's just
> > more code to maintain compared to your way. You only need to track
> > one delta (1.0 -> 1.1 ... -> latest) and publish two files latest.exe
> > and update.zip
> 
> Sometimes I think that CVS or SVN may be the simplest solution to update
> applications.  Install a client on the target computer, it may be
> invisible to the user, copy the CVS or SVN directories, and provide a
> script the does (also invisible) 'cvs up -r version_a_b'.
> 
> Thomas
> --
> http://mail.python.org/mailman/listinfo/python-list
>



More information about the Python-list mailing list