nanonyme edited a comment on issue #1385: URL: https://github.com/apache/buildstream/issues/1385#issuecomment-808932066
> Not exactly, you don’t need to use a git submodule to use the junction plugin, rather we would have the `bst-plugins-experimental` repo provide a `project.conf` which declares all the plugins as local plugins _there_ (so a plugins package itself _is_ a buildstream project without any elements), then any project can use explicitly versioned plugins across a junction using the junction plugin origin (the version like you say, can be a git tag, it is defined by the `Source` on that junction). > Also, as I believe we had settled on keeping the `tar` and `remote` sources in core, it is more likely that plugin repos will be consumed as tarball releases through the `junction` origin rather than as git tags (although it is conceivable to use a tar plugin just to obtain the git plugin and then use the git plugin from there). So lemme get this straight: could we publish bst-plugins-experimental into PyPI in such a way that the resultant tarball could be directly depended on as a plugin source using version pinning? Just, the tarball published into PyPI would have project.conf and declare all the plugins as local plugins. So basically you would then get to choose between installing it directly or depending on it through your BuildStream dependencies. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
