| Summary: | dev-util/buildbot-0.7.2 (new ebuild) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Michael Schmid <meheschmid> |
| Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | djc |
| Priority: | High | Keywords: | EBUILD |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://buildbot.sourceforge.net/ | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
The ebuild
init.d script for buildbot sample conf.d configuration file |
||
|
Description
Michael Schmid
2006-05-11 05:28:15 UTC
Created attachment 86604 [details]
The ebuild
First revision of the ebuild. Maybe a bit too verbose, if a native english speaker could shorten the text a bit it'd be nice.
Created attachment 86605 [details]
init.d script for buildbot
Simple init.d script to start one or more buildbot masters/slaves. I found no other way to set the variables for HOME and so on to make it work. Passing them using start-stop-daemon -e didn't work when I tried, after a build started these variables were overridden by the ones from the shell the script was started in, resulting in failure.
Created attachment 86606 [details]
sample conf.d configuration file
I would like to have this in Portage! Thanks for the ebuild. Just committed dev-util/buildbot-0.7.4 with some changes: removed the pkg_config: imho this is not worth it since you will have to edit the generated files anyway and running the "buildbot" tool directly is not harder than the emerge --config is. Also limited the init script to a single instance: if you want more than one just symlink or copy the script, which has the benefit you can restart them separately. Closing this bug, please file a new one if there are problems with the ebuild. |
