public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] {OT} Development framework with access restriction?
Date: Mon, 3 Oct 2011 18:00:55 -0400	[thread overview]
Message-ID: <CA+czFiDipZLynEYD07d8mzcrugQ325NxT1_huyrCGEi6UuuhNg@mail.gmail.com> (raw)
In-Reply-To: <CAN0CFw2-COXcuMQDg+Bsjojp5oVtpn0osU3dcFHKZK-1GQTNZA@mail.gmail.com>

On Mon, Oct 3, 2011 at 5:54 PM, Grant <emailgrant@gmail.com> wrote:
>>> I think separate repositories would only be necessary when using
>>> distributed version control (git) as opposed to centralized
>>> (subversion).  I think subversion's path-based authorization should
>>> eliminate the need for separate repositories?
>>>
>>
>> Separate repos aren't strictly necessary, but it's much harder to verify
>> your path permissions than it is to verify that your repositories are
>> separate.
>>
>> The first involves config files and cascading information; the second
>> involves being able to count to two =)
>
> Would multiple repos work in a scenario where different developers
> have access to different stuff and some stuff should be accessible to
> multiple devs?  I don't think you want the same stuff in more than one
> repo.  It seems like managing multiple repos would get out of hand in
> that sort of situation and I might be better off with config files and
> a single repo.

With SVN, you do have 'externals' available:
http://svnbook.red-bean.com/en/1.0/ch07s03.html

Where I work, externals are used for holding common code like large
libraries which are needed or useful to multiple projects.

-- 
:wq



  reply	other threads:[~2011-10-03 22:03 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-26 20:01 [gentoo-user] {OT} Development framework with access restriction? Grant
2011-09-26 21:37 ` Michael Orlitzky
2011-09-27 11:27   ` Mick
2011-09-29  1:18   ` Grant
2011-09-29  2:23     ` Grant
2011-09-29  6:57       ` Jonas de Buhr
2011-09-29  7:32         ` Mick
2011-09-30 23:53           ` Grant
2011-10-01 11:07             ` Florian Philipp
2011-10-01 23:27               ` Grant
2011-10-02 22:41                 ` Mick
2011-10-03 22:01                   ` Grant
2011-10-03 22:12                     ` Michael Mol
2011-09-29  8:13       ` Neil Bothwick
2011-09-29 17:23         ` Michael Orlitzky
2011-09-30 23:59           ` Grant
2011-10-01  0:23             ` Michael Orlitzky
2011-10-01 23:46               ` Grant
2011-10-02 19:04                 ` Michael Orlitzky
2011-10-03 21:54                   ` Grant
2011-10-03 22:00                     ` Michael Mol [this message]
2011-10-04  4:25                     ` Michael Orlitzky
2011-09-27 12:19 ` Jonas de Buhr
2011-09-29  1:23   ` Grant
2011-09-29  6:43     ` Jonas de Buhr
2011-09-30 23:50       ` Grant
  -- strict thread matches above, loose matches on Subject: below --
2011-10-01  5:58 Pandu Poluan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+czFiDipZLynEYD07d8mzcrugQ325NxT1_huyrCGEi6UuuhNg@mail.gmail.com \
    --to=mikemol@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox