Alan McKinnon <alan.mckin...@gmail.com> wrote:
> On 14/12/2015 23:06, cov...@ccs.covici.com wrote:
> > Michael Orlitzky <m...@gentoo.org> wrote:
> >
> >> On 12/14/2015 02:18 PM, cov...@ccs.covici.com wrote:
> >>> Hi. I have a regular ebuild for app-accessibility/brltty and I want to
> >>> create a .9999 ebuild out of it, so it gets from the latest .git
> >>> version. Is there a way I can do that -- either some documentation on
> >>> how to do it, or some hints? Is there a general method for doing this?
> >>>
> >>> Thanks in advance for any suggestions.
> >>>
> >>
> >> Look for -9999 ebuilds in the tree using the git-r3 eclass, and copy
> >> what they do. It's not fancy but something like
> >>
> >> $ find ./ -name '*-9999.ebuild' | xargs grep -l 'git-r3'
> >>
> >> in PORTDIR should turn up a bunch of examples.
> >
> > OK, I will take a look.
> >
> >
>
> If the sources are in regular old git, the main changes are to replace
> SRC_URI with EGIT_REPO_URI and to inherit git-2. Here's one of mine I
> slapped together:
>
>
> EAPI=5
> inherit eutils user git-2 python-single-r1
> EGIT_REPO_URI="https://github.com/SiCKRAGETV/SickRage.git";
> DESCRIPTION="SickRage - Searches TheTVDB for TV shows"
> HOMEPAGE="http://www.sickrage.tv/";
> LICENSE="GPL-3" # only
> SLOT="0"
> KEYWORDS="~amd64 ~x86"
> IUSE=""
>
>
> The rest of the ebuild is completely stock standard stuff so I omitted
> it for clarity. You may need to rm a bunch of stuff in src_install()
> that comes with the git repo and you don't want to be merged.
OK, I have one question more -- for the git, I need to run ./autogen
before I can run configure, do I need to put that in source_prepare, or
is this done automatically?
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
cov...@ccs.covici.com
