| Summary: | sci-biology/biopython-9999: new ebuild to build from git master | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Martin Mokrejš <mmokrejs> |
| Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | enhancement | CC: | python, sci-biology |
| Priority: | High | Keywords: | EBUILD |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | biopython-9999.ebuild | ||
Created attachment 223177 [details]
biopython-9999.ebuild
This is based on biopython-1.53.ebuild
You don't need explicit src_unpack().
Inheriting of git eclass as the last eclass causes that git_src_prepare() overrides distutils_src_prepare() as implementation of src_prepare(), so you should define explicit src_prepare():
src_prepare() {
git_src_prepare
distutils_src_prepare
}
Thanks, that works: >>> Emerging (1 of 1) sci-biology/biopython-9999 * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * CPV: sci-biology/biopython-9999 * REPO: gentoo * USE: elibc_glibc kernel_linux mysql userland_GNU x86 >>> Unpacking source... * GIT update --> * repository: git://github.com/biopython/biopython.git * at the commit: a3c6b432e7ea2379febd5c0e5750222107f0d908 * branch: master * storage directory: "/usr/portage/distfiles/git-src/biopython" Initialized empty Git repository in /var/tmp/portage/sci-biology/biopython-9999/work/biopython-9999/.git/ >>> Unpacked to /var/tmp/portage/sci-biology/biopython-9999/work/biopython-9999 >>> Source unpacked in /var/tmp/portage/sci-biology/biopython-9999/work >>> Preparing source in /var/tmp/portage/sci-biology/biopython-9999/work/biopython-9999 ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/sci-biology/biopython-9999/work/biopython-9999 ... >>> Source configured. >>> Compiling source in /var/tmp/portage/sci-biology/biopython-9999/work/biopython-9999 ... * Building of sci-biology/biopython-9999 with CPython 2.6... python2.6 setup.py build -b build Anyway, in case one would want to apply a patch in src_unpack(), what to do with the CPything thing? ;-) Perhaps something for the overlay Martin, perhaps you should get access to the overlay, so that you can place your contributions there. |
Biopython is actively and quickly being developed and I sometimes need the trunk. I hacked an ebuild which works for me. However, somehow the distutils portage stuff adds "-2.6" to the "${S}" string because I have python 2.6. If somebody could fix the ugly hack it would be great and could be committed into the tree. Thanks! ;-)