[pLog-svn] Best way to create incremental releases/patches?

[Oscar Renalias]

I don't think it's too difficult to create such a script, but the
problem is that checking out two different trees just to see which
files changes is going to be a costly operation (specially considering
how big our source code tree is)

I will give it a try as soon as I can...

Oscar

On 8/31/05, Benjamin Krause <ork at orkland.de> wrote:
> Oscar Renalias wrote:
> > Now that plog 1.0.2 is near, many people requested in previous
> > versions to release an incremental update which only included the
> > files that changed from plog 1.0.1 to 1.0.2 (which would make the
> > package much smaller) Before I attempt to create a script to automate
> > this, does anybody know if there is any tool out there to do it? Is it
> > even remotely possible to do it?
> >
> > I am thinking that the only way is to check out the current release as
> > well as the last one, compare all the files and then get only those
> > ones that changed. But if you know a better way to do that, I'd like
> > to know :)
> 
> Hey Oscar,
> 
> i dont think there is any other fast way to do it .. compare each files
> checksum and build a tar file containing the changed and the new files.
> doesn't sound like a lot of fun :)
> how about implementing some sort of auto-update in pLog, where the admin
> can checkout files directly in the admin interface if svn is installed?
> 
> might be not that much more work then to build a checkout and compare
> script, but would add a nice feature :)
> on the other hand, not a lot of hosters will have a svn client installed
> on their machines..
> 
> ben
> _______________________________________________
> pLog-svn mailing list
> pLog-svn at devel.plogworld.net
> http://devel.plogworld.net/mailman/listinfo/plog-svn
>