Hello fellow gophers, I'm trying to package serf[1] for Fedora. As a result, I've filed a few review requests[2]. Most of those were super easy to do and that isn't really what this email is about assuming that running go test in %check is the proper way to do things. I took a spec from one of lsm5's packages and went from there (but added the testing stage).
Some of the packages that serf depends on such as github.com/vmihailenco/bufio have relative imports of the package in the tests and as a result, refuse to build outside of $GOPATH. The issue with this is that is makes it impossible for me to currently test building this with rpmbuild, mock, or koji. I've filed an issue with the upstream maintainer[3], but am curious if there is anything else that could be done to handle this? Also, labix.org/v2/mgo/bson is stored in bzr. They will occasionally do a release, but don't provide tarballs. I've also sent an email to their list[4] asking if there is a way to get the release as a tarball. In lieu of pristine upstream sources, what is the "proper" fedora packaging thing to do? Finally, while I've created rpms as part of $dayjob for 5+ years, I've never contributed them back to Fedora/Redhat and thought it was high time to fix that. Other than filing the review requests, what else is there I need to do for having these packages sponsored? Thanks in advance! [1] http://www.serfdom.io [2] https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=VERIFIED&bug_status=ASSIGNED&email1=jeffschroeder%40computer.org&emailassigned_to1=1&emailcc1=1&emailreporter1=1&emailtype1=exact&list_id=2172542 [3] https://github.com/vmihailenco/bufio/issues/4 [4] https://groups.google.com/forum/#!topic/mgo-users/5RU_mTQfbKs -- Jeff Schroeder Don't drink and derive, alcohol and analysis don't mix. http://www.digitalprognosis.com
_______________________________________________ golang mailing list [email protected] https://lists.fedoraproject.org/mailman/listinfo/golang
