walters added a new comment to an issue you are following:
``
So...I am still uncertain about the distinct paths of:
1) Build fork of host&platform
2) Build on top of host&platform
The "fork" option carries with it a lot of maintenance overhead imposed by the
modularity build system - we'll have distinct binaries as well, and that's going
to invalidate some of the testing.
The "build on top" thing brings in a requirement to modularize all of the build
dependencies. I know there's a prototype "autotools" module for example,
but taking this out requires modules for a vast array of stuff, from `golang` out to
corner cases like `gtk-doc` (currently requires perl), etc.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/312