[gentoo-user] creating a .9999 ebuild

[gentoo-user] creating a .9999 ebuild

[covici]

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.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] creating a .9999 ebuild

[Michael Orlitzky]

On 12/14/2015 02:18 PM, covici@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.

Re: [gentoo-user] creating a .9999 ebuild

[covici]

Michael Orlitzky <mjo@gentoo.org> wrote:

> On 12/14/2015 02:18 PM, covici@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.


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] creating a .9999 ebuild

[Alan McKinnon]

On 14/12/2015 23:06, covici@ccs.covici.com wrote:
> Michael Orlitzky <mjo@gentoo.org> wrote:
> 
>> On 12/14/2015 02:18 PM, covici@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.


-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] creating a .9999 ebuild

[Michael Orlitzky]

On 12/14/2015 04:38 PM, Alan McKinnon wrote:
> 
> 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:

git-2 is deprecated in favor of git-r3. Don't ask me about the naming
scheme.


> KEYWORDS="~amd64 ~x86"

It doesn't matter for an overlay, but -9999 ebuilds should never be
keyworded. Empty KEYWORDS="" is preferred. That may silence a repoman
warning if you're getting one.

Re: [gentoo-user] creating a .9999 ebuild

[covici]

Alan McKinnon <alan.mckinnon@gmail.com> wrote:

> On 14/12/2015 23:06, covici@ccs.covici.com wrote:
> > Michael Orlitzky <mjo@gentoo.org> wrote:
> > 
> >> On 12/14/2015 02:18 PM, covici@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
         covici@ccs.covici.com

Re: [gentoo-user] creating a .9999 ebuild

[Jc García]

2015-12-14 16:13 GMT-06:00  <covici@ccs.covici.com>:

> 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?

That should mean the package you are building is using autotools as a
build system, so you should inherit the autotools eclass and run
eautoreconf in src_prepare(). I remember this is stuff that it's in
the dev manual, that should be the place you should be looking mostly.

PD: knowing the build system also helps a lot

Re: [gentoo-user] creating a .9999 ebuild

[covici]

Jc García <jyo.garcia@gmail.com> wrote:

> 2015-12-14 16:13 GMT-06:00  <covici@ccs.covici.com>:
> 
> > 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?
> 
> That should mean the package you are building is using autotools as a
> build system, so you should inherit the autotools eclass and run
> eautoreconf in src_prepare(). I remember this is stuff that it's in
> the dev manual, that should be the place you should be looking mostly.
> 
> PD: knowing the build system also helps a lot
> 

Well, I did get it done, had to put a make  in the ebuild to create some
documents which was not there in the regular ebuild, and I had to run
autogen myself because of the peculiar way the author upstream does his
builds, but it did work.  Very handy to be able to do this kind of
thing.

Thanks all.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

[gentoo-user] Re: creating a .9999 ebuild

[James]

 <covici <at> ccs.covici.com> writes:


> Well, I did get it done, had to put a make  in the ebuild to create some
> documents which was not there in the regular ebuild, and I had to run
> autogen myself because of the peculiar way the author upstream does his
> builds, but it did work.  Very handy to be able to do this kind of thing.

It would be great to have something in the gentoo wiki about this sort of 
9999.ebuild stuff, particularly if it is kept current and edgy.... Linking
in to the latest (experimental) repoman would also help. Maybe much of this
is in github combined with a few examples ?

I'd like to see an example doc on EAPI=6 .9999 builds and such. Dev oriented
documents are great but it also helps to have "cookbooks".  If something
like this exists, even in blog posts or forum links, I'd be grateful for
that info.


James