LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices

Reply
 
Search this Thread
Old 05-04-2006, 12:16 PM   #1
annekaelber
Member
 
Registered: Sep 2003
Location: Mesa, AZ
Distribution: Slackware
Posts: 49

Rep: Reputation: 15
Understanding Subversion checkout result?


Hello,

I am contemplating shifting from CVS to Subversion (SVN). I tried a test import from my CVS repository to a new SVN repo. Then, I checked out my work into a test work directory. The results I got have me wondering if SVN is really going to work for me.

First, I'm not a code developer, I'm a writer. In my home directory, I have a directory called writing. In that directory there are further divisions: ~/writing/fiction/, ~/writing/ideas/, ~/writing/support/ ...and so on. I usually work in one directory per story and a novel has several directories to cover those tidbits of information I collect that don't go into the novel.

However, in the test SVN checkout directory, I have a totally different picture. Instead of seeing my work, I'm greeted with a chaos of tags and branches. Some of my work is in the trunk directory and some is scattered in tags or branches. Is this right? Is this the way SVN works? I saw FAQ topics fretting the .svn directory, but none that addressed my concerns: why my work is spread across this chaos?

In the meantime, I wonder if there's some other tool out there that would be better suited to helping me track edits and changes in my work. Expecting responses that cover the editing abilities of most word processors: I don't use them. I work in simple, beautiful, plain text (and then bring in the big guns: LaTeX!).

Thanks in advance to any SVN or CVS afficionados or other writers who see this and take the time to reply. This community is my favorite place to come for answers.

Anne.
 
Old 05-04-2006, 11:19 PM   #2
leandean
Member
 
Registered: Oct 2005
Location: Burley, WA
Distribution: Sabayon
Posts: 276

Rep: Reputation: Disabled
you can convert to subversion via ::

http://subversion.tigris.org/faq.html#cvs2svn

Importing is problematic at best.
 
Old 05-04-2006, 11:29 PM   #3
annekaelber
Member
 
Registered: Sep 2003
Location: Mesa, AZ
Distribution: Slackware
Posts: 49

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by leandean
you can convert to subversion via ::
Yep, that's how I got to the point I was discussing in my original post. I've done the conversion (at least a test run) and I've done a checkout. What I've got now in my working directory makes a pile of spaghetti look easy to untangle. This is such a departure from what I expected to see that I wonder if I'm doing it right.

Anne.
 
Old 03-24-2007, 09:20 AM   #4
Mehmet Karatay
LQ Newbie
 
Registered: Nov 2006
Location: Edinburgh
Distribution: Red Had Enterprise Edition (work) , Fedora Core 6 (home), PCLinuxOS (laptop)
Posts: 4

Rep: Reputation: 0
I know this is a bit late, but it might help others.

Subversion does split the work into trunk, branches, and tags as you say, but when you do a checkout you specify then which you want. i.e.

svn co url_to_repository/trunk/project

As I'm guessing you know from the documentation the trunk if for the main project. In development terms (I know this doesn't apply as a writer) this is where the latest working version is kept.

The branches are where you can keep variations to the work, and actively work on them. The tags simply provide the equivalent of a symbolic link to a certain revision whether that's in a branch or the trunk. This means instead of having to remember the revision number you can refer to it by a specific name. For example

svn co url_to_repository/tags/sent_to_editor

Once you have the repository set up and running, you don't check it out from the root repository directory so you don't have to deal with branches, trunk, and tags each time.

In your case if you're not going to be experimenting with different versions to your text then simply using trunk all the time, with a tag every now and then to refer to a specific past snapshot might be best? It sounds like you can just ignore branches. Once you've made them you won't ever have to remember that they are there if you don't want to.

Hope this helps,

mehmet
 
  


Reply

Tags
cvs, subversion, svn


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Document Checkout? kemplej Linux - Software 1 03-09-2006 06:19 PM
cvs checkout on slackware 8.1 rolandp Linux - Software 1 06-30-2005 12:20 AM
Checkout these firefox video ads reddazz General 3 05-13-2005 01:16 AM
Stop anonymous CVSROOT checkout Whitman Linux - Software 0 10-08-2004 06:31 PM
How to install Subversion(Version Control with Subversion) under RedHat Linux. netkiller Linux - Networking 1 07-01-2004 05:45 AM


All times are GMT -5. The time now is 07:24 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration