On Thu, Aug 30, 2018 at 5:06 PM Derek Gaston <fried...@gmail.com> wrote:
> On Thu, Aug 30, 2018 at 4:36 PM Paul T. Bauman <ptbau...@gmail.com> wrote:
>
>> You guys get the blame for this one. There was insistence from MOOSE
>> developers that the bootstrapped build system be included in the master
>> tree. I was against it.
>>
>
> No way. It wasn't in the old build system - and is in the new. YOU were
> the one who was trying to take away a feature (multiple simultaneous builds
> with different METHODS) that *everyone* was (and had been for a long time
> and still is) actually using to get features *you* wanted with Automake.
>
If we didn't include the bootstrapped build system in the master tree,
there would be no diffs when the build system was updated, except for
Makefile.am or configure.ac, whichever piece was updated. MOOSE developers
insisted those be included in the new build system. Thus we have separate
bootstrap commits.
> All we did was complain (in the same way you are now when I suggested we
> remove build system features) that something we use everyday was going away.
>
Including the bootstrapped build system or not in the master tree has no
effect on the METHODS feature. If we did not include the bootstrapped build
system in the master tree there would be no diffs and no need for bootstrap
commits. I would be in favor of removing the bootstrapped parts of the
build system from the master tree.
>
> I will agree that what we ended up with was a compromise that isn't the
> best. I'm not saying we try to fix it within the current build system...
> but it is something I would like to fix in a new one.
>
> Derek
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
