Re: [gentoo-user] EAPI-6 dev-python ebuilds
On Mon, 21 Mar 2016 15:50:02 + James wrote - > Hello, > > I'm looking for some EAPI-6 examples or ebuild templates to > to review. > > > Is there a simple way to parse the portage tree for EAPI=6 examples > regardless if they are testing, stable or still just beta in a git > repo somewhere? Maybe a particular dev has already revised a group > of ebuilds and I just need to search out, by dev, a list of packages and > recent date of ebuilds to find a cache of EAPI=6 ebuilds to parse? > (not sure how to proceed on this hunch). > > > # qgrep -H EAPI=5 wstools-0.4.3.ebuild > dev-python/wstools/wstools-0.4.3.ebuild:EAPI=5 > > works for a specific file, but I want to parse the entire /dev-python > portion of the portage tree. Is there a more robust tool? Maybe I should > just patch the qgrep applet to suite my needs (hardest option)? cd /usr/portage/dev-python grep -r -l "EAPI=5" * |grep 'ebuild$' Not particularly efficient, but for "one-offs"... Dave F
[gentoo-user] EAPI-6 dev-python ebuilds
Hello, I'm looking for some EAPI-6 examples or ebuild templates to to review. Is there a simple way to parse the portage tree for EAPI=6 examples regardless if they are testing, stable or still just beta in a git repo somewhere? Maybe a particular dev has already revised a group of ebuilds and I just need to search out, by dev, a list of packages and recent date of ebuilds to find a cache of EAPI=6 ebuilds to parse? (not sure how to proceed on this hunch). # qgrep -H EAPI=5 wstools-0.4.3.ebuild dev-python/wstools/wstools-0.4.3.ebuild:EAPI=5 works for a specific file, but I want to parse the entire /dev-python portion of the portage tree. Is there a more robust tool? Maybe I should just patch the qgrep applet to suite my needs (hardest option)? Is there a recommended cache of EAPI=6 ebuilds I can look at, particularly to note differences in the EAPI=6 versus their EAPI=5 older sibling ebuilds? Any guidance is welcome. James
[gentoo-user] Eapi 6 ?
Howdy, I've read snippets that EAPI 6 will provide a mechanism for follks to put patches directly into ebuilds. I'm not certain (some discussion needed) that this will eliminated some ebuilds from my /usr/local/portage development repository. However, now I'm learning and hacking on 2 different bleeding edge technologies. Clusters (mesos, spark etc etc) and Java (maven etc etc). I am but a follwer at this time on those two bleeding edge fronts. But codes are release at multiple times during the day/week that I need to test. So, in my limited understanding, EAPI 6 looks absolutely wonderful. So, since I'm only hacking at ebuilds for my own needs (currently not able to produce anything that is not embarrashing) can I start building ebuilds that use EAPI-6? I understand that it is not finalized yet. But, if the user supplied patching is at least workable, I'd rather get busy learning/testing those new EAPI-6 tricks. thoughts and comments and insight are most welcome. James
Re: [gentoo-user] Eapi 6 ?
On Tue, Sep 16, 2014 at 2:30 PM, James wirel...@tampabay.rr.com wrote: So, since I'm only hacking at ebuilds for my own needs (currently not able to produce anything that is not embarrashing) can I start building ebuilds that use EAPI-6? I understand that it is not finalized yet. But, if the user supplied patching is at least workable, I'd rather get busy learning/testing those new EAPI-6 tricks. User patching already exists, but ebuilds have to support it for it to work by calling epatch_user during src_prepare(). EAPI6 will make calling this mandatory, and will put it in the default phase function. So, 100% of EAPI6 ebuilds will support it, though many ebuilds already support it otherwise. All you need to do is add epatch_user to src_prepare in an existing ebuild to use it. If you want to patch the build system you'll also need to make calls to autotools/etc as needed after calling epatch_user. -- Rich
Re: [gentoo-user] Eapi 6 ?
On Tue, 16 Sep 2014 14:38:12 -0400, Rich Freeman wrote:
All you need to do is add epatch_user to src_prepare in an existing
ebuild to use it. If you want to patch the build system you'll also
need to make calls to autotools/etc as needed after calling
epatch_user.
You can often do it without touching the ebuild at all by putting
post_src_unpack() {
cd ${S}
epatch_user
}
in /etc/portage/env/category/package[-version]
--
Neil Bothwick
No trees were harmed in the sending of this message. However, a large
number of electrons were terribly inconvenienced.
signature.asc
Description: PGP signature
