You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildstream.apache.org by GitBox <gi...@apache.org> on 2021/03/29 05:58:42 UTC
[GitHub] [buildstream] gtristan edited a comment on issue #1385: Cache keys must be stable indefinitely
gtristan edited a comment on issue #1385:
URL: https://github.com/apache/buildstream/issues/1385#issuecomment-809086285
> 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.
**Yes**.
Remember that plugins are loaded into per-project namespaces, so multiple projects which depend on eachother (through junctions) can safely depend on *different versions* of `bst-plugins-experimental` this way.
Notice the *tip* in [the documentation about the junction plugin origin](https://docs.buildstream.build/master/format_project.html#junction-plugins) which discusses *"Distributing plugins as projects"*.
--
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:
users@infra.apache.org