[GitHub] [buildstream] gtristan commented on issue #1791: [bst-1] BST to warn if there is a conflicting config

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

gtristan commented on issue #1791:
URL: https://github.com/apache/buildstream/issues/1791#issuecomment-1328952188

   Hi,
   
   The plugins which a project.conf declares as "local" (loaded from a project directory), cannot be accessed by any other project (in bst1), they cannot be override plugins in a subproject or be accessed from another junctioning project.
   
   Plugin names are also not forced to be unique across loaded projects.
   
   In BuildStream 2, the project summary printed in advance of the build is very meticulous about describing the origins of each plugin which was loaded as a consequence of loading the build graph, this was more necessary since with BuildStream 2 you can use/load plugins from subprojects across junctions.
   
   Do I understand correctly that:
     * You have a plugin named "foo" in project A
     * You have another plugin also named "foo" in project B which junctions project A
     * When building elements in project B, different "foo" plugins will be used in project A and project B, and this is confusing
   
   Would more elaborate information about the loaded projects and what plugins are being loaded in each project (similar to how we log in bst2) be helpful here ?
   
   Here is an example of the loaded project information at the beginning of the build log in bst2 for reference: https://docs.buildstream.build/master/junctions/junction-elements.html#building-and-running


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