Some newbie questions

[Jens Vonderheide <vo...@redlink.de>]

Hi,

I am new to subversion (just installed it). After reading the book, faq
and mailing list, some questions remain.

I plan to use subversion with a software that is currently under CVS control.
With CVS, I created a branch after each release and used this branch for
bugfixes and the trunk for new development. Is this method recommended for
subversion as well? And can I assign a sort of symbolic name to this
branch so that the branch name itself is different for each release (e.g.
"release-030919"), but the most recent release is also available as
"release"?

Some files are used in more than one project. If I put all these projects
into the same repository, is there a way to link these files togehter so
that a change to one position of this file is duplicated in all other?

And last but not least, has anyone written a script (like acu for CVS) to
always keep the trunk checked out? Shouldn't be that hard using the
post-commit hook, but if anyone has already done that, I could save that
work.

Thanks in advance,

Jens Vonderheide

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Some newbie questions

[su...@collab.net]

>> With CVS, I created a branch after each release and used this branch
>> for bugfixes and the trunk for new development. Is this method
>> recommended for subversion as well? And can I assign a sort of
>> symbolic name to this branch so that the branch name itself is
>> different for each release (e.g. "release-030919"),

I guess you didn't read chapter 4, which is all about how to create
branches?  :-)

>> but the most recent release is also available as "release"?

Branches and tags are just directories;  so the only way to do this is to
copy the latest tag directory to 'release'.  Then when a new tag comes out,
delete the 'release' directory, and recreate it as a copy of the latest tag.
You'll have to recreate the 'release' directory every time.

>> Some files are used in more than one project. If I put all these
>> projects into the same repository, is there a way to link these files
>> togehter so that a change to one position of this file is duplicated
>> in all other?
>
> check the book for "svn:externals" about that.


I don't think he's talking about working copies, I think he's talking about
repository changes being replicated via hard-links.  And the answer
is "no":  at this time, the repository only contains files and directories,
no hard or soft links.




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Some newbie questions

[SteveKing <st...@gmx.ch>]

----- Original Message ----- 
From: "Jens Vonderheide" <vo...@redlink.de>

> I plan to use subversion with a software that is currently under CVS
control.
> With CVS, I created a branch after each release and used this branch for
> bugfixes and the trunk for new development. Is this method recommended for
> subversion as well? And can I assign a sort of symbolic name to this
> branch so that the branch name itself is different for each release (e.g.
> "release-030919"), but the most recent release is also available as
> "release"?

Sure you can do that with subversion. It's just a little different than with
CVS.
If you create a repository for each project, then add the following folders
to it with your first import:
/trunk/
/branches/
/tags/

Now import your files to /trunk/. That's where you're working on.
If you now create a branch just make a "copy" from trunk
to /branches/branchname/
That's where you can work on too. But if you want to make a "release"
then make a copy to /tags/release-x.x.x/.
Just make sure that you don't commit changes to the tags folder.

> Some files are used in more than one project. If I put all these projects
> into the same repository, is there a way to link these files togehter so
> that a change to one position of this file is duplicated in all other?

check the book for "svn:externals" about that.

Stefan


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org