SEO

Hi,

I want to create an ebuild for myself but I do need some rather unusual
stuff.

The ebuild will be for a package which will require quite a lot of
patches (and some of these are broken and cant be applied to the package
root directory directly but instead have to be applied somewhere deep
within the package).

Also there is no autoconf / automake support and thus I'll first need to
compile everything myself and then install a lot of shared libs and
binaries myself.

As of now I've only found the documentation in the gentoo dev handbook
about ebuilds but this one really lacks information about my case.

Browsing through some other ebuilds I found out that I'll have to use a
crossover between mplayer and nedits ebuilds. However, I've found zero
docs about some of the custom stuff these ebuilds use (like nedit
inheriting gcc? and then using stuff like:

into /usr
dobin source/nedit
exeinto /usr/bin

Would anyone know a howto / document covering such things or will I have
to RTFS?

In principle I've got my ebuild up and running but I really doubt that
cp'ing my binaries into /usr/bin and alike (using patch and other utils
directly instead of eg epatch) is a good idea in terms of ever unmerging
the package...

kind regards Philip

Philip Lawatsch wrote:

> Hi,
>
> I want to create an ebuild for myself but I do need some rather unusual
> stuff.
>
> The ebuild will be for a package which will require quite a lot of
> patches (and some of these are broken and cant be applied to the package
> root directory directly but instead have to be applied somewhere deep
> within the package).

inherit eutils and use epatch. cd to the right directory before.

> Also there is no autoconf / automake support and thus I'll first need to
> compile everything myself and then install a lot of shared libs and
> binaries myself.
>
> As of now I've only found the documentation in the gentoo dev handbook
> about ebuilds but this one really lacks information about my case.
>
> Browsing through some other ebuilds I found out that I'll have to use a
> crossover between mplayer and nedits ebuilds. However, I've found zero
> docs about some of the custom stuff these ebuilds use (like nedit
> inheriting gcc?

I don't think it is documented anywhere.

> and then using stuff like:
>
> into /usr
> dobin source/nedit
> exeinto /usr/bin

These functions are documented in the developer handbook and in man 5
ebuild.

> Would anyone know a howto / document covering such things or will I have
> to RTFS?

There is also [1], which can be of help sometimes.

hth, Dennis

[1] http://dev.gentoo.org/~ciaranm/docs/IGNORE_the-doc/

Dennis Nienhüser wrote:


>>Also there is no autoconf / automake support and thus I'll first need to
>>compile everything myself and then install a lot of shared libs and
>>binaries myself.
>>
>>As of now I've only found the documentation in the gentoo dev handbook
>>about ebuilds but this one really lacks information about my case.
>>
>>Browsing through some other ebuilds I found out that I'll have to use a
>>crossover between mplayer and nedits ebuilds. However, I've found zero
>>docs about some of the custom stuff these ebuilds use (like nedit
>>inheriting gcc?
>
>
> I don't think it is documented anywhere.

Sigh, already feared that.

>>and then using stuff like:
>>
>>into /usr
>>dobin source/nedit
>>exeinto /usr/bin
>
>
> These functions are documented in the developer handbook and in man 5
> ebuild.

Ok, my bad, but the documentation is not really good.

I'd like / I have to create quite a big directory tree in /opt/my_stuff
containing roughly 15 subdirs, lots of shared objects and so on.
Examples / more detailed docs would be welcome


>>Would anyone know a howto / document covering such things or will I have
>>to RTFS?
>
>
> There is also [1], which can be of help sometimes.
>
> hth, Dennis
>
> [1] http://dev.gentoo.org/~ciaranm/docs/IGNORE_the-doc/


Nice pointer, thanks a lot for this one!

kind regards Philip

Philip Lawatsch enlightened us with:
> I want to create an ebuild for myself but I do need some rather unusual
> stuff.

Check out /usr/portage/skel.ebuild.

> However, I've found zero docs about some of the custom stuff these
> ebuilds use (like nedit inheriting gcc? and then using stuff like:

man 5 ebuild

Sybren
--
The problem with the world is stupidity. Not saying there should be a
capital punishment for stupidity, but why don't we just take the
safety labels off of everything and let the problem solve itself?

Sybren Stuvel wrote:
> Philip Lawatsch enlightened us with:
>
>>I want to create an ebuild for myself but I do need some rather unusual
>>stuff.
>
>
> Check out /usr/portage/skel.ebuild.

This one really just covers the very basic stuff.

>>However, I've found zero docs about some of the custom stuff these
>>ebuilds use (like nedit inheriting gcc? and then using stuff like:

> man 5 ebuild

Not quote the docs I wanted either since I know how to use ebuild but
not how / what to do inside the ebuild.

Anyway, after some hundered lines of

insinto doins and insopts

I finally managed to do what I wanted to.

kind regards -ph-