[GitHub] [buildstream] gtristan opened a new issue #1555: Ensure core plugins are shadowed by explicitly loaded plugins

[GitBox <gi...@apache.org>]

gtristan opened a new issue #1555:
URL: https://github.com/apache/buildstream/issues/1555


   At this time the core BuildStream codebase has no way of adding new core plugins as plugin names share the same namespace.
   
   It was decided in [the january 5th meeting](https://lists.apache.org/thread/d7fgbdnfx62b4v1mz8g8qq56ohm3kjmz) that the most elegant way to address this is to simply ensure that explicitly loaded plugins *shadow* plugin names from the core - if the core ever exposes a new plugin which collides with a user's plugin name - then it will not break the project, and the user can readjust the project if they want to leverage the new plugin.
   


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [buildstream] gtristan closed issue #1555: Ensure core plugins are shadowed by explicitly loaded plugins

[GitBox <gi...@apache.org>]

gtristan closed issue #1555:
URL: https://github.com/apache/buildstream/issues/1555


   


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org