On Tue, 16 Apr 2019 at 12:38, Rajdeep Bharati wrote: > > I think one more port needs to be created: autobahn. > (https://docs.buildbot.net/current/manual/installation/requirements.html)
If it's not in the ports tree yet, I believe I have this port on my computer already. (I can check when I come home and submit it to spare you some extra work.) The reason I didn't submit it was because each version introduced a zillion incompatibilities with the previous version and the port where I would have needed it no longer worked with the latest version anyway. (Otherwise you can always use pypi2port and put it under python/py-autobahn. Maybe that would already work out of the box? You can try to install and use pypi2port via macports to do the legwork for you when creating the py-autobahn package; or potentially try the new upt, but that one is not yet tested and not yet merged to be used as a simple "port install". Or simply wait a bit.) > About the npm dependencies: Can't it be taken care of by using buildbot-www > from pypi? This could definitely be packaged as a separate port. I'm not sure if this belongs under python/py-buildbot-www or simply next to the existing buildbot port. It doesn't seem to be a regular python module, so maybe the latter? I would need to check it to see where the individual files should go. Can these be installed system-wide and used for multiple masters or do they belong next to each individual project? That package seems to contain just static files, I don't see any npm dependencies there? (I don't care if we initially need to run npm manually as long as it's documented what to do.) (I probably need to try it out on my computer when I come home to be able to give you a slightly more competent answer. And maybe check what other distros are doing / how they package it.) Mojca
