Mehdi Amini via llvm-dev
2016-Sep-03 23:37 UTC
[llvm-dev] [RFC] One or many git repositories?
> On Sep 3, 2016, at 3:04 PM, Patrice Kouame <pkouame at mac.com> wrote: > > > +1 for keeping it separate.Can you clarify what you referring to specifically? This sub thread (the last 4 messages) started with a mention of GCC dependencies. It is not clear to me how to relate to llvm now. Mehdi> > One can easily set up a git subproject structure if the need is pressing... > > Patrice > >> On Sep 3, 2016, at 5:39 PM, Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> >>> 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 >> >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> 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/20160903/fd666f64/attachment.html>
Patrice Kouame via llvm-dev
2016-Sep-04 01:05 UTC
[llvm-dev] [RFC] One or many git repositories?
Someone mentioned llvm in a mono repository below...> On Sep 3, 2016, at 7:37 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > > >> On Sep 3, 2016, at 3:04 PM, Patrice Kouame <pkouame at mac.com> wrote: >> >> >> +1 for keeping it separate. > > Can you clarify what you referring to specifically? > This sub thread (the last 4 messages) started with a mention of GCC dependencies. It is not clear to me how to relate to llvm now. > > Mehdi > >> >> One can easily set up a git subproject structure if the need is pressing... >> >> Patrice >> >>> On Sep 3, 2016, at 5:39 PM, Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> >>> >>>> 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 >>> >>> _______________________________________________ >>> LLVM Developers mailing list >>> llvm-dev at lists.llvm.org >>> 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/20160903/5694c099/attachment.html>
Mehdi Amini via llvm-dev
2016-Sep-04 02:59 UTC
[llvm-dev] [RFC] One or many git repositories?
> On Sep 3, 2016, at 6:05 PM, Patrice Kouame <pkouame at mac.com> wrote: > > Someone mentioned llvm in a mono repository below…Right, we actually have a proposal to take what is in the current SVN repo here: http://llvm.org/svn/llvm-project/ and migrate this to a single repository. I was not sure if you were referring to this proposal (monorepo) or to the recent emails about “external libraries” that GCC uses like gmp and mpfr. You can find more details here: https://reviews.llvm.org/D24167 If you have some good reasons why you would think a proposal would be problematic to you, or one would better fit your workflow, feel free to expose them now. Best, — Mehdi> > On Sep 3, 2016, at 7:37 PM, Mehdi Amini <mehdi.amini at apple.com <mailto:mehdi.amini at apple.com>> wrote: > >> >> >> On Sep 3, 2016, at 3:04 PM, Patrice Kouame <pkouame at mac.com <mailto:pkouame at mac.com>> wrote: >> >>> >>> +1 for keeping it separate. >> >> Can you clarify what you referring to specifically? >> This sub thread (the last 4 messages) started with a mention of GCC dependencies. It is not clear to me how to relate to llvm now. >> >> Mehdi >> >>> >>> One can easily set up a git subproject structure if the need is pressing... >>> >>> Patrice >>> >>>> On Sep 3, 2016, at 5:39 PM, Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >>>> >>>> >>>>> On Sep 2, 2016, at 12:33 PM, Dimitry Andric via llvm-dev <llvm-dev at lists.llvm.org <mailto: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 <mailto: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 >>>> >>>> _______________________________________________ >>>> 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/20160903/146eb388/attachment.html>