Re: [BuildStream] Create new containers-related and Python-related plugins repos
- From: Jürg Billeter <j bitron ch>
- To: Sander Striker <s striker striker nl>, Chiara Tolentino <ctolentino3891 gmail com>
- Cc: buildstream-list gnome org
- Subject: Re: [BuildStream] Create new containers-related and Python-related plugins repos
- Date: Wed, 31 Oct 2018 18:26:57 +0100
Hi,
On Wed, 2018-10-31 at 11:34 +0000, Sander Striker via BuildStream-list
wrote:
As this would introduce a breaking change, this should ideally be
merged before the release of BuildStream v1.4.
Please let me know your ideas regarding this proposal.
I'd like us to consider going further earlier and removing all but the import,
junction, and abstract elements from BuildStream itself and moving that to
a plugins repository. We can still bundle these in the release if we want
to, but it sets us on the path of maintaining the plugins separate from the
core. It also prevents future discussions on what plugins should be in the
buildstream repository, and which shouldn't.
I generally like the separation. However, if we still bundle them in
the releases, we don't really improve the situation. The question would
simply change from 'what plugins should be in the core repo' to 'what
plugins should be bundled with core releases'. On the other hand simply
dropping them from core would break compatibility.
Is there a transition plan I'm not aware of that solves this?
Jürg
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]