| 1 |
On Mon, Oct 3, 2011 at 5:54 PM, Grant <emailgrant@×××××.com> wrote: |
| 2 |
>>> I think separate repositories would only be necessary when using |
| 3 |
>>> distributed version control (git) as opposed to centralized |
| 4 |
>>> (subversion). I think subversion's path-based authorization should |
| 5 |
>>> eliminate the need for separate repositories? |
| 6 |
>>> |
| 7 |
>> |
| 8 |
>> Separate repos aren't strictly necessary, but it's much harder to verify |
| 9 |
>> your path permissions than it is to verify that your repositories are |
| 10 |
>> separate. |
| 11 |
>> |
| 12 |
>> The first involves config files and cascading information; the second |
| 13 |
>> involves being able to count to two =) |
| 14 |
> |
| 15 |
> Would multiple repos work in a scenario where different developers |
| 16 |
> have access to different stuff and some stuff should be accessible to |
| 17 |
> multiple devs? I don't think you want the same stuff in more than one |
| 18 |
> repo. It seems like managing multiple repos would get out of hand in |
| 19 |
> that sort of situation and I might be better off with config files and |
| 20 |
> a single repo. |
| 21 |
|
| 22 |
With SVN, you do have 'externals' available: |
| 23 |
http://svnbook.red-bean.com/en/1.0/ch07s03.html |
| 24 |
|
| 25 |
Where I work, externals are used for holding common code like large |
| 26 |
libraries which are needed or useful to multiple projects. |
| 27 |
|
| 28 |
-- |
| 29 |
:wq |
Archives