| Summary: | be-9999.ebuild (New Package) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | W. Trevor King <wking> |
| Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
| Status: | CONFIRMED --- | ||
| Severity: | enhancement | Keywords: | EBUILD |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://bugseverywhere.org/ | ||
| Whiteboard: | sunrise-suggested | ||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Ebuild against cjb@laptop.org-20091006145647-kqkmoh481tl5hvt4
Adjust to Gentoo's docbook2man naming conventions. Override BE default install into $HOME Don't try to build libbe/_version.py in the BE Makefile ChangeLog for be ebuild Metadata for BEebuild Manifest for all of the above a new more QA prone ebuild |
||
|
Description
W. Trevor King
2010-02-07 15:35:03 UTC
Created attachment 218815 [details] Ebuild against cjb@laptop.org-20091006145647-kqkmoh481tl5hvt4 Ebuild against Bazaar trunk (as of revision cjb@laptop.org-20091006145647-kqkmoh481tl5hvt4). I'm a little embarrassed by the src_prepare definition, but libbe/_version.py needs access to the bzr repository somehow... Created attachment 218817 [details, diff] Adjust to Gentoo's docbook2man naming conventions. See http://bugs.gentoo.org/205703 Created attachment 218819 [details, diff]
Override BE default install into $HOME
Created attachment 218821 [details, diff]
Don't try to build libbe/_version.py in the BE Makefile
The ebuild handles this directly, because the Makefile will eventually be run in an exported snapshot, not a full-fledged branch.
Created attachment 218823 [details]
ChangeLog for be ebuild
Created attachment 218825 [details]
Metadata for BEebuild
Created attachment 218827 [details]
Manifest for all of the above
Hello, The Gentoo Team would like to firstly thank you for your ebuild submission. We also apologize for not being able to accommodate you in a timely manner. There are simply too many new packages. Allow me to use this opportunity to introduce you to Gentoo Sunrise. The sunrise overlay[1] is a overlay for Gentoo which we allow trusted users to commit to and all users can have ebuilds reviewed by Gentoo devs for entry into the overlay. So, the sunrise team is suggesting that you look into this and submit your ebuild to the overlay where even *you* can commit to. =) Thanks, On behalf of the Gentoo Sunrise Team, Justin. [1]: http://www.gentoo.org/proj/en/sunrise/ [2]: http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq Created attachment 230151 [details]
a new more QA prone ebuild
I used be today and i got the time to improve the ebuild, making it respecting more QA and using the distutils eclass. Yeah i know i'm using also python.eclass but since distutils inherit it, and this will unlikely change i left it as is. I added the ~amd64 keyword since it works on amd64 here.
Hope it will be usefull :)
(In reply to comment #9) > Hope it will be usefull :) Thanks! I've updated your version for the new Git-versioned BE: http://gitorious.org/be/ I've bundled my new version into my overlay: http://www.physics.drexel.edu/~wking/code/git/git.php?p=wtk-overlay.git http://www.physics.drexel.edu/~wking/code/git/wtk-overlay.git/ http://www.physics.drexel.edu/~wking/code/layman.xml Use at own risk and all of that ;). I've published the be-9999.ebuild and in my Gentoo overlay. See http://www.physics.drexel.edu/~wking/unfolding-disasters/posts/Gentoo_overlay/ Layman XML (for listing in /etc/layman/layman.cfg overlays): http://www.physics.drexel.edu/~wking/unfolding-disasters/posts/Gentoo_overlay/layman.xml Future updates to the ebuild will go into that repository, which saves me from having to post new versions here when I have to make changes to stay abreast of upstream developments. |
