Re: [gentoo-dev] Ebuild questions

[Brett I. Holcomb]

Crumbs, my first reply went to Christian instead of the list.

Thank you.  I went back and reread that document - I guess I'd forgotten 
about that section.  I've been reading man pages, eclasses, and existing 
ebuilds so I guess my brain overflowed!  That has helped a lot - along with 
rereading some of the eclasses I've printed.  At this point I have my ebuild 
retrieving the cvs files and unpacking them (that's easy with cvs.eclass <G>) 
and I'm about to get it to compile.  I had to make my own src_compile that 
uses some egames.class functions.  

This is fun!  I haven't done any shell programming on unix/Linux for about 15 
years (I've been working VMS systems and have done a lot of DCL work there 
and I have done some extensive Windows batch - but that hardly counts <G>).

I'll dig into some of the eclasses and see what they do.  I'd like to stay 
with whatever standards we have - it's just finding out about them all <G>.

> > I've been working on creating an ebuild this week and after working with
>
> it I
>
> > have some questions about how ebuilds work.
>
> nice :)
>
> > 1.  I assume that if I add no functions to an ebuild the process is A)
>
> src_unpack, B) src_compile, C) src_install.  In other words there are
> three
>
> > steps or functions that will be executed.  If I desire I can make my own
>
> functions for these but if I don't I get these three steps executed by
> emerge.
>
> Right, but there is more to the story, read section "2. ebuild scripts" in
> the link 0. There it is documented 10 such standard functions. For those
> of which you do not provide in your ebuild, emerge will do the default
> functions.
>
> [0] http://www.gentoo.org/doc/en/gentoo-howto.xml
>
> > 2.  What is the best way to let the user know what's happening - for
>
> example,
>
> > "compiling xyz module now".  I notice some builds use einfo to put out
>
> messages about what you have to do after install (add user to groups,
> etc).
>
> > Are there specific ebuild functions I should use or are plain old echo
>
> statements okay?
>
> the pkg_postinst function is often used to place information about what to
> after the install, I think using einfo and ewarn is good practice.
>
> > Thanks.
>
> np,
>
> > --
> >
> > Brett I. Holcomb
> > AKA Grunt <><
> >
> > --
> > gentoo-dev@g.o mailing list
>
> Christian

-- 

Brett I. Holcomb
AKA Grunt <><

--
gentoo-dev@g.o mailing list