2 questions

[gxk <gx...@gmail.com>]

My company installed Subversion and i should put there files,
which is whole GTK project.
1. what better way to keep such project: vanilla tarballs + patches
or just opened source code?
2. The whole project placed at some common repository. Do i need
separate repository? Why?

Gery

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

Re: 2 questions

[Ryan Schmidt <su...@ryandesign.com>]

On Sep 6, 2006, at 14:37, gxk wrote:

> My company installed Subversion and i should put there files,
> which is whole GTK project.
> 1. what better way to keep such project: vanilla tarballs + patches
> or just opened source code?

If you're keeping a copy of another project in your own repository,  
like the GTK source code, you will probably want to read the entire  
chapter on vendor branches:

http://svnbook.red-bean.com/en/1.2/svn.advanced.vendorbr.html

I recommend keeping the unpacked source code in your repository, not  
compressed or archived files.


> 2. The whole project placed at some common repository. Do i need
> separate repository? Why?

It's up to you whether to store everything in a single repository or  
make multiple repositories. There are pros and cons to both  
approaches. So far, I personally have kept all my projects and vendor  
items together in a single repository.



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