|
![](/i/fill.gif) |
On 13/04/2012 09:46 AM, Warp wrote:
> Darren New<dne### [at] san rr com> wrote:
>> On 4/11/2012 2:57, Warp wrote:
>>> Who thought this would be a good idea?
>
>> On the other hand, it prevents you from having to check out the entire
>> repository just to get one project.
>
> Shouldn't different projects go into different branches?
Depends on your SCM I suppose.
I know that, for example, GHC is managed as several interrelated
projects. GHC is a Haskell compiler written in Haskell, and as such
depends on the Haskell standard libraries, which are separate from the
actual compiler. The test suite is also a separate project. But all of
these projects live in the same source tree, so you can actually build
the compiler...
What it means is that you can, for example, update the test suite,
independent of any particular compiler version. Or if there's a
performance improvement to one of the standard libraries, you can
rebuild the compiler with that, without actually changing the compiler.
Stuff like that.
Post a reply to this message
|
![](/i/fill.gif) |