|
On 27/02/2019 10:08, William Salmon via
buildstream-list wrote:
So the aim hear is to make it easier to maintain more plugins and by nothaving too many as "core" it should encourage "Buildstream" to make it as easy as possible to add in extra plugins via project.conf.In my opinion, If this change results in OS'es needing to package all the plugins then this has failed in its original aim. I'd prefer it if existing packaging tools got all the useful plugins with BuildStream, that is, 'apt install BuildStream' or 'pip3 install BuildStream' automatically installed bst-external or whatever contains git, tar etc., by means of a dependency. Having BuildStream fetch plugins itself sounds like implementing our own package manager. Also, I expect to have external network access when running 'apt install'; I don't when running 'bst', so it would be annoying for BuildStream to say it needed more network access on first run when I reasonably expected it'd installed it using apt. Jim |