[gentoo-dev] ebuild questions

[gentoo-dev] ebuild questions

[Hector Urtubia]

Hey,
I just installed gentoo and I love it. I also started writing some ebuilds, 
but I ran into some questions:
1.- How does ebuild fill the CONTENTS file of a package when installing ??
The problem that I had is that some programs kept track of its installation 
files into the CONTENTS file, and some did not. I know that using the scripts 
on /usr/lib/portage/bin work, but only _some_ makefiles register the programs 
correctly.

2.- How do I submit new ebuilds?? So far I have ebuilds for ladspa and 
terminatorX. I'm planning to do a couple more :)

Thanks, and keep those ebuilds coming!

Hector U.

[gentoo-dev] Ebuild questions

[Brett I. Holcomb]

If this is the wrong list for this question please tell me where to move it 
but it doesn't seem to fit gentoo-user or any of the others.

I want to do an ebuild for some programs but have never done one.  I've read 
the Gentoo docs on ebuilds and eclasses and the man pages for ebuild.  
However, in looking at some ebuilds - noticably flight gear and wine-cvs I 
see variables such a $PV defined.  The docs mention $P but not $PV or other 
variables.  I've browsed some of the eclasses trying to find the definitions 
and haven't been successful.  Where are these explained.  Are there any more 
docs I can read?

Thanks.

-- 

Brett I. Holcomb
AKA Grunt <><

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Ebuild questions

[Brian Jackson]

# man 5 ebuild
is pretty up to date
other than that, I would just look through others that do something similar 
and see how they do things

--Brian

On Tuesday 10 June 2003 08:49 pm, Brett I. Holcomb wrote:
> If this is the wrong list for this question please tell me where to move it
> but it doesn't seem to fit gentoo-user or any of the others.
>
> I want to do an ebuild for some programs but have never done one.  I've
> read the Gentoo docs on ebuilds and eclasses and the man pages for ebuild.
> However, in looking at some ebuilds - noticably flight gear and wine-cvs I
> see variables such a $PV defined.  The docs mention $P but not $PV or other
> variables.  I've browsed some of the eclasses trying to find the
> definitions and haven't been successful.  Where are these explained.  Are
> there any more docs I can read?
>
> Thanks.

-- 
OpenGFS -- http://opengfs.sourceforge.net
Home -- http://www.brianandsara.net


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Ebuild questions

[Brett I. Holcomb]

Yes, thanks.  I found it today.  I thought I tried that list night but I bet 
I did man 1 ebuild!  


> # man 5 ebuild
> is pretty up to date
> other than that, I would just look through others that do something similar
> and see how they do things
>
> --Brian
>
> On Tuesday 10 June 2003 08:49 pm, Brett I. Holcomb wrote:
> > If this is the wrong list for this question please tell me where to move
> > it but it doesn't seem to fit gentoo-user or any of the others.
> >
> > I want to do an ebuild for some programs but have never done one.  I've
> > read the Gentoo docs on ebuilds and eclasses and the man pages for
> > ebuild. However, in looking at some ebuilds - noticably flight gear and
> > wine-cvs I see variables such a $PV defined.  The docs mention $P but not
> > $PV or other variables.  I've browsed some of the eclasses trying to find
> > the definitions and haven't been successful.  Where are these explained. 
> > Are there any more docs I can read?
> >
> > Thanks.

-- 

Brett I. Holcomb
AKA Grunt <><

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Ebuild questions

[Kumba]

I think this question is more geared towards gentoo-user, but ${PV} and 
${PN} are offshoots of ${P}.  Basically, if ${P} stands for "Package 
Name & Version", then ${PV} and ${PN} hold the Version and Name of the 
package specifically.  Others of note are ${A}, which I believe is the 
archive (i.e., the tarball), ${S} for Source Directory.  ${WORKDIR} and 
${FILESDIR} and ${DISTFILES} should all be self-explanatory (I think 
${DISTFILES} exists).

As for additional documentation on these, they might be in the other 
docs, but you probably will have to just study random ebuilds.

--Kumba



Brett I. Holcomb wrote:

> If this is the wrong list for this question please tell me where to move it 
> but it doesn't seem to fit gentoo-user or any of the others.
> 
> I want to do an ebuild for some programs but have never done one.  I've read 
> the Gentoo docs on ebuilds and eclasses and the man pages for ebuild.  
> However, in looking at some ebuilds - noticably flight gear and wine-cvs I 
> see variables such a $PV defined.  The docs mention $P but not $PV or other 
> variables.  I've browsed some of the eclasses trying to find the definitions 
> and haven't been successful.  Where are these explained.  Are there any more 
> docs I can read?
> 
> Thanks.
> 



--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Ebuild questions

[Patrick Kursawe]

[-- Attachment #1: Type: text/plain, Size: 535 bytes --]

On Tue, Jun 10, 2003 at 09:49:32PM -0400, Brett I. Holcomb wrote:
> The docs mention $P but not $PV or other 
> variables.  I've browsed some of the eclasses trying to find the definitions 
> and haven't been successful.  Where are these explained.  Are there any more 
> docs I can read?

On http://www.gentoo.org/doc/en/gentoo-howto.xml you will find a tiny hint
saying:

Note: There is a manpage which talks about the internal format, variables
and function s in an ebuild script: man 5 ebuild. 

Have fun,

Patrick	

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Ebuild questions

[brett holcomb]

Hmm, I am going blind! I missed the reference.  When I get 
to my Gentoo machine I'll read man 5 ebuild.

Thanks.

On Wed, 11 Jun 2003 08:41:28 +0200
  Patrick Kursawe <phosphan@gentoo.org> wrote:
>On Tue, Jun 10, 2003 at 09:49:32PM -0400, Brett I. 
>Holcomb wrote:
>> The docs mention $P but not $PV or other 
>> variables.  I've browsed some of the eclasses trying to 
>>find the definitions 
>> and haven't been successful.  Where are these explained. 
>> Are there any more 
>> docs I can read?
>
>On http://www.gentoo.org/doc/en/gentoo-howto.xml you will 
>find a tiny hint
>saying:
>
>Note: There is a manpage which talks about the internal 
>format, variables
>and function s in an ebuild script: man 5 ebuild. 
>
>Have fun,
>
>Patrick	


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Ebuild questions

[Paul de Vrieze]

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1101 bytes --]

On Wednesday 11 June 2003 03:49, Brett I. Holcomb wrote:
> If this is the wrong list for this question please tell me where to move it
> but it doesn't seem to fit gentoo-user or any of the others.
>
> I want to do an ebuild for some programs but have never done one.  I've
> read the Gentoo docs on ebuilds and eclasses and the man pages for ebuild.
> However, in looking at some ebuilds - noticably flight gear and wine-cvs I
> see variables such a $PV defined.  The docs mention $P but not $PV or other
> variables.  I've browsed some of the eclasses trying to find the
> definitions and haven't been successful.  Where are these explained.  Are
> there any more docs I can read?
>

Welcome to the club, it's not that hard. And don't start to look at either of 
those ebuilds, it are complicated ones for "misbehaving" programs. Try 
looking at some "clean" kde ebuilds using the kde eclass. (They are often 
10-liners, with 5 lines being occupied by headers and witespace)

Paul

-- 
Paul de Vrieze
Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.cs.kun.nl/~pauldv

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-dev] Ebuild questions

[Brett I. Holcomb]

I've been working on creating an ebuild this week and after working with it I 
have some questions about how ebuilds work.

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.

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?


Thanks.

-- 

Brett I. Holcomb
AKA Grunt <><

--
gentoo-dev@gentoo.org mailing list

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@gentoo.org mailing list
>
> Christian

-- 

Brett I. Holcomb
AKA Grunt <><

--
gentoo-dev@gentoo.org mailing list