This PR is mostly followup of [0]. It contains 3 commits which can be cherry-picked if needed.
1) First I wanted to document a way to disable the ~boostrap suffix if needed [1].
2) Then I think we should get back to bcond_with macro, although the syntax is not really understandable.
3) The last commit tries to describe how to do the bootstrap build. I used it in practice for rubygem-cucumber bootstrap [2, 3].
Also, I have considered if part of this bellongs to Dist Tag guidelines, not sure.
One missing bit is that this could be nice to use together with modules, because modules allow to define macros. So with_bootstrap 1 defined in module allows to bootstrap all components of module and later one (revert) commit to remove the macro definition enables the official build without any change to other packages. Not sure I really want to have it documented.
This PR is mostly followup of [0]. It contains 3 commits which can be cherry-picked if needed.
1) First I wanted to document a way to disable the
~boostrapsuffix if needed [1].2) Then I think we should get back to
bcond_withmacro, although the syntax is not really understandable.3) The last commit tries to describe how to do the bootstrap build. I used it in practice for rubygem-cucumber bootstrap [2, 3].
Also, I have considered if part of this bellongs to
Dist Tagguidelines, not sure.One missing bit is that this could be nice to use together with modules, because modules allow to define macros. So
with_bootstrap 1defined in module allows to bootstrap all components of module and later one (revert) commit to remove the macro definition enables the official build without any change to other packages. Not sure I really want to have it documented.