Hi,
Yesterday while tinkering with buildstream I realised that cmake
projects were building twice. As my builds take so long I decided I
might as well create a PR.
https://github.com/apache/buildstream-plugins/issues/92
https://github.com/apache/buildstream-plugins/pull/93
As you'll see there, I was pointed out that such fixes would incur in a
policy violation. Now, while we don't want to break anything, it sounds
like we also should be able to come up with a mechanism. I am not as
well-versed in the buildstreams than others here, so I'll appreciate any
ideas.
It occurs to me, for example, that we can have some elements with a
-next postfix and these do not abide by the cache key stability rule.
Once bst 3 is released, the -next elements can be folded back into their
stable ones and we'll also know we have well-tested elements to release
instead of doing them all at once.
HTH,
Aleix
