No. Of course I can use the GU and cause it to find the librariesI, but I don't care if I can do something that way. I have to be able to find where that information is stored, how it gets its defaults, what uses it, when it is updated and why.
This is just table stakes for using this tool in a work environment. The library issues have stopped our evaluation of this tool as is, and I have moved on to trying to figure out what it would take to clean up things like this. The problem is, it appears to actively be moving in the wrong direction... it is actively trying to do nonsense on GitHub and force the use of preinstalled libraries... that is fine for a toy but not for real work.
The code is not very complex, it should be easy to fix and add proper functionality for repositories. But my concern is as was pointed out
I'm not interested in doing the work if it isn't going to go upstream. Let's see if I can figure out what is really going on with all these paths, variables, tables and 'plugins', and how much actual work it would be to really make it rational (that is, not lead to nasty surprises) and functional (that is, actually provide versioned, repo backed library management) first...