On Jan 26, 2016, at 5:09 AM, Amar Takhar wrote: > On 2016-01-26 07:56 -0500, Craig Treleaven wrote: >> Hi: >> >> I???m attempting to set up a Mac OS X buildbot slave for the MythTV project. >> >> They haven???t had a Mac builder for several years and so I need to >> temporarily set up a buildbot master to work out the build process. >> However, >> my initial attempts have been stymied by the sqlalchemy / sqlalchemy-migrate >> situation. > <snip> > > Awesome, they really need it. > > I run a lot of Mac workers I have only had luck running in a stable fashion > by using virtualenv and having pip or setup.py install all the dependencies > for > me. > > I would try that rather than relying on macports or another package manager.
I am a manager of the MacPorts project, and I also want to use the buildbot master and slave as installed by MacPorts. I have no experience with virtualenv and no particular desire to learn yet another way to install software, having standardized on MacPorts some time ago. Rather, I would like to offer software in MacPorts that is functional, and that includes the buildbot master and slave. If what we are offering in MacPorts right now is not functional, what do we need to change to make it functional? The Python infrastructure in MacPorts is not designed to accommodate multiple versions of a single Python module being installed simultaneously. If it is really the case that buildbot, especially master, requires very specific versions of its dependencies, and cannot tolerate them being updated, how can that unfortunate situation be rectified? _______________________________________________ users mailing list [email protected] https://lists.buildbot.net/mailman/listinfo/users
