llvm dev - Sep 2016 - [RFC] One or many git repositories?

As someone that has worked with both gcc and llvm,

One thing about gcc that drives me bat-guano-crazy is that
First you check out gcc, try to build it, and find that you also
Need mpc, so you check that out and try to build it, and
Find out you also need gmp, so you check that out and try
To build it, and find out that you also need mpfr, .....

IE I'm in favor of a mono-repository.

Also I'll ask that for a change that spans multiple
projects (eg clang, llvm, lto) simultaneously is there
any alternative to mono-repository that supports
an atomic commit ???  (IMHO maintaining repo
integrity and consistency is the number one priority)


--Peter Lawrence.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20160815/002b6815/attachment.html>

Here is the draft: https://reviews.llvm.org/D24167

— 
Mehdi



> On Aug 15, 2016, at 3:12 PM, Lawrence, Peter via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> As someone that has worked with both gcc and llvm,
>  
> One thing about gcc that drives me bat-guano-crazy is that
> First you check out gcc, try to build it, and find that you also
> Need mpc, so you check that out and try to build it, and
> Find out you also need gmp, so you check that out and try
> To build it, and find out that you also need mpfr, …..
>  
> IE I’m in favor of a mono-repository.
>  
> Also I’ll ask that for a change that spans multiple
> projects (eg clang, llvm, lto) simultaneously is there
> any alternative to mono-repository that supports
> an atomic commit ???  (IMHO maintaining repo
> integrity and consistency is the number one priority)
>  
>  
> --Peter Lawrence.
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
<http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20160901/f053e764/attachment.html>

On 16 Aug 2016, at 00:12, Lawrence, Peter via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> As someone that has worked with both gcc and llvm,
> 
> One thing about gcc that drives me bat-guano-crazy is that
> First you check out gcc, try to build it, and find that you also
> Need mpc, so you check that out and try to build it, and
> Find out you also need gmp, so you check that out and try
> To build it, and find out that you also need mpfr, …..
I can understand your frustration, but these are all completely external
libraries, and it does not really make sense to include this into any
mono-repository.

For example, you are also dependent on libc headers, are you going to include
these into your repository?  And kernel headers?  The end result will possibly
include half of GitHub into that mono-repository... :)

So as usual, for any open source project, read the requirements first, and
install those from whatever your local package management system is.

If LLVM is going to use a mono-repository, it should only include LLVM
components, in my opinion.

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: Message signed with OpenPGP using GPGMail
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20160902/55198199/attachment.sig>

> On Sep 2, 2016, at 12:33 PM, Dimitry Andric via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> On 16 Aug 2016, at 00:12, Lawrence, Peter via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
>> 
>> As someone that has worked with both gcc and llvm,
>> 
>> One thing about gcc that drives me bat-guano-crazy is that
>> First you check out gcc, try to build it, and find that you also
>> Need mpc, so you check that out and try to build it, and
>> Find out you also need gmp, so you check that out and try
>> To build it, and find out that you also need mpfr, …..
> 
> I can understand your frustration, but these are all completely external
libraries, and it does not really make sense to include this into any
mono-repository.
> 
> For example, you are also dependent on libc headers, are you going to
include these into your repository?  And kernel headers?  The end result will
possibly include half of GitHub into that mono-repository... :)
> 
> So as usual, for any open source project, read the requirements first, and
install those from whatever your local package management system is.
> 
> If LLVM is going to use a mono-repository, it should only include LLVM
components, in my opinion.
This seems a good principle in general, but note that we already included
external projects in the repo. Out-of-my-head right now I can think of the
google tests library, and ISL.

— 
Mehdi