[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Is this newbie crazy? Using svn to manage a xampp install

From: <hansbkk_at_gmail.com>
Date: 2007-04-20 06:39:14 CEST

I'm a big fan of XAMPP, and using it in "no-install" mode so it's
portable via my USB memory stick.

I'm manually managing my install regarding updates - keeping a log of
files I've modified, using the archive bit to backup changed files,
etc. but really the process is a mess and very prone to human error.

Every time I upgrade to the latest XAMPP I'm terrified it's going to
break my server, so I manually copy every file myself, diff the config
files before overwriting, etc. what a bore. . .

So I've got the idea of importing my whole xampp tree into its own
repository and letting svn do all this automagically for me! Am I
crazy or what?

I thought I'd do some research first on how to get the mime-type
property set automatically at import/add time - maybe to something
custom? for the various binary types dll/exe, but of course I want to
make sure the .conf and other such text files are stored as text.

One problem, I'm not sure of the impact, is that the location path of
the working xampp installation itself changes depending on what
machine I'm running it from - sometimes it's x:\xampp, other times
it's d:\hans\thumb\big\xampp and so on. There's a whole batch of conf
and other files that get automatically updated by the setup_xampp.bat
(via AWK I think) whenever I want to change its running location.

What would people suggest as a way to track those files separately
from the ones that "I human" have manually edited? In other words, if
the only change is to the path statements, I don't want them flagged
as changed?

Right now my idea would be to "reset" the paths back to a "standard"
location each time before committing the tree, so the paths match
those in the current head versions. Maybe SUBST a seldom-used drive
letter so the path is X:\xampp and run the setup batch file before
doing any commit?

Simple, but not very elegant - other ideas?

And feedback on the whole idea is especially welcome, I reckon if it's
a good idea I would have found some past threads in my googling around
and I haven't. . .

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 20 06:39:34 2007

This is an archived mail posted to the Subversion Users mailing list.