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

Re: Dumb newby question: moving from RCS

From: Kevin Grover <kevin_at_kevingrover.net>
Date: Tue, 20 Jan 2009 16:14:19 -0800

On Tue, Jan 20, 2009 at 2:44 PM, Michael Dixon <
michael.dixon_at_denovosoftware.com> wrote:

> postmaster_at_tigris.org wrote:
> > With Perl apps, there's no "make" and "release" -- the checked-in
> ["committed"] files *ARE* the app, and so part of the workflow isn't clear
> to me: I have the hierarchy PROJECT. PROJECT/SVN is my repository and
> PROJECT/PROJECT is where the actual in-production app lives [together with
> its various "extra" files: logs, docs, config files, etc]. I can easily
> right-click on SVN, do "check out a copy" into PROJECT/NEWSTUFF, play
> around, and then do a "commit" on the whole directory [so everything I
> changed and tweaked would get "checked in" -- that's the right way to do an
> SVN-styule workflow, yes?]
> >
> Just to clarify, because from your wording I can't tell whether you're
> clear on the concept: Subversion is a client/server application. The
> master copy of your repository doesn't live in PROJECT/SVN; it lives on
> the server. (The server may of course be running on the same machine as
> you run the client and do your work, but the server is logically
> separate from your working area.)
>

True about the client server. Not necessarily true about this repo.

He could have created a repo in PROJECT\SVN and access it via the file://
protocol. I assumed as much. I would recommend that he put them somewhere
else (I used c:\repos\svn\*, where * is a dir per repository, under Windows)
and then use svnserve. However, since he's having problems with this part
of svn, I didn't want to add to the confusion.

OP: You can tell using the TSVN (or Explorer) 'Properteries' tab, or using
CLI "svn info".

The key point to keep in mind: there is ONE repository and MANY working
copies. You must have at least one working copy (for normal usage).

> Other than that, yes, the workflow is correct. Rightclick a folder and
> then check out a working copy *from the server* to PROJECT/NEWSTUFF,
> make your changes, and then commit to send your changes to the server.
>
> When you're ready to make your changes live, copy the files from an
> updated working copy to your production folder (PROJECT/PROJECT).
>
> btw, you probably want to keep your docs and config files versioned too.
>
> -Mike
>
> ------------------------------------------------------
>
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1039481
>
> To unsubscribe from this discussion, e-mail: [
> users-unsubscribe_at_tortoisesvn.tigris.org].
>
Received on 2009-01-21 01:14:35 CET

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