psabata added a new comment to an issue you are following:
``
A couple of things here.
* the "fork" option implies a lot of overhead indeed, however, most of it can be
automated with simple scripts here and there -- automatic depsolving on dist-git changes,
automatic rebuilds, that's all possible;
* building on top of H&P is not only about having the build dependencies available, it
also relies on currently undefined behavior where your module updates packages owned by
another module (Atomic Host updating/overriding Host & Platform content in this case);
we intend to make this impossible in the long term so I'm not sure how this would
work
* if Atomic Host is just a Platform profile, you cannot actually change anything in the
sources -- no custom patches, minimized builds or alternative implementations; not even
different versions of anything; furthermore, what is actually installed in the composed
OSTree is defined in the JSON file, not the module (although I would be awesome if we
could generate it from a profile later on)
Regarding `atomic-build-deps`, such a module would be more or less identical to
`bootstrap` and I would discourage you from pursuing that path.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/312