How does one manage different branches that contain a few files with a
few lines of static "localized" changes. I've re-read the Branches &
Merging section of the book, and I'm wondering if I'm missing
something.
I would like to use Subversion to manage both the production & staging
servers for a website (for which I have only FTP access). There are
two areas of particular interest for me, but I imagine this is a more
generic problem. Personally, I want to change one line in a CSS file
and three lines in a db-config file so that my staging site has a
strong visual cue and uses a staging database. I imagine that a
traditionally installed application with localizations for various
sites may have similar needs.
Obviously, in my case, it's not a huge issue, but this is a personal
project I'm pursuing so I can learn to do things right. I'd be curious
how a similar problem of larger scale is solved.
My guess is that I'll have an eternal branch called "production" where
I will make extremely few changes: (the four lines I mentioned
earlier). Each time I want to push a version into production, I will
merge the eternal branch with trunk, accept all changes, and then tag
& publish (not sure I need that last step).
Right now I have a post-commit script that FTPs all relevant changes
to staging. I also have a shell script that will do a clean build on
production given a revision & path.
Basically, I think I'm looking for #IFDEF ( ... if I got that right,
my C days are getting hazy)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Apr 8 12:43:35 2006