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

Newbie Help -- Directory Structure, File Lists

From: <trlists_at_clayst.com>
Date: 2004-11-21 01:16:11 CET

Hi Folks ...

I'm new to subversion and have a few questions.

I am a single developer working on Windows. Most of what I do ends up
on Linux webservers and I do have a couple of Linux boxes here
(firewall, internal server), but to keep things simple let's just stick
to Windows for now as that's where I have svn installed (W2K).

So my normal mode is to bop along developing and testing something, and
getting others to test it, until it is ready to release. With svn I'll
probably keep track of it a little more carefully and save some of the
intermediate points but that's not crucial.

Once it's out in the world I need to keep two branches -- current
working release where I add bug fixes, and development version where I
hack away and change things all around in order to rework a feature or
add new ones. These generally correspond to version uplaoded, at least
from time to time if not at every commit, to live and test areas on the
client's web server. Here I really do need version control, taking
snapshots in zip files won't cut it.

In subversion terms (as far as I understand them from reading), which
of these (debugging released version vs. development code for new
features) would you make the trunk and which would you make a copy or
"private branch"? As far as I can see it could be done either way, I'm
wondering if there are advantages to one approach or the other.
Whichever way it's done, they'll always be merged back together
eventually.

Another more specific question -- can I tell svn to use a file
containing a list of files? I definitely have unversioned stuff in my
project directories, and a command like svn add @filelist (or, as it's
done in Windows, type filelist | svn add) would be very helpful. If
it's not there I can work around it with scripts but it would be a
help. The docs don't suggest anything for this as far as I can see but
I was hoping ...

Now back to Linux and Windows ... any advantage for me as a single
developer to putting the repository on my Linux fileserver and
accessing it across my internal LAN from the Windows box? Local
storage seemed simpler but if I'm missing something there I'd like to
know -- for example is BDB more stable on Linux, or are there other
operational advantages?.

Thanks much,

Tom

--
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Nov 21 01:18:02 2004

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