keeping slrn-svn + patches up to date (was: Strange behaviour with identity.sl and accented characters)

* Troy Piggins on Wednesday, November 28, 2007 at 14:10:47 +1000
> Maybe a touch OT, but when using svn like the command in my sig below, if I'm
> in a directory that has never downloaded slrn before, the whole slrn source
> code is placed in a dir called "slrn".  I cd to that dir, configure, make, and
> sudo make install.  All good.
> 
> If I use the same svn command again, I assume what it does is just update the
> modified files?  So I can just go into that slrn dir again and compile again?
> Probably need to "make clean" first.
> 
> But if I've applied one of Rudy's patches and compiled with that, does that svn
> command overwrite all of the files that the patch had updated as well as any
> modified source ones?
> 
> To date I have not been sure, so I just "rm -rf slrn/" and download the whole
> source tree every time then apply the patch.

Personally I keep a Mercurial (http://www.selenic.com/mercurial/)
mirror of the svn repository, and use Mercurial's patch queue
extension to apply the patches. -- If you intend to go that route
you can mail me for more info.

Another way would be to create a local mirror of the current
source without the svn-history overhead and apply the patches
inside the mirror:

$ svn co https://slrn.svn.sourceforge.net/svnroot/slrn/trunk slrn
$ rsync -avc --delete --exclude='.svn' slrn/ slrn-patched/
$ cd slrn-patched
$ patch [... etc.]
$ cd ../slrn
$ svn update
$ cd ..
$ rsync -avc --delete --exclude='.svn' slrn/ slrn-patched/
$ cd slrn-patched
$ patch [... etc.]

c
-- 
_B A U S T E L L E N_ lesen! --->> <http://www.blacktrash.org/baustellen.html>

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4