Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Paul de Vrieze <pauldv@g.o>
Subject: Re: Ebuild questions
Date: Wed, 11 Jun 2003 11:05:18 +0200
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@...
Homepage: http://www.cs.kun.nl/~pauldv
Attachment:
pgp1F4IaWomHQ.pgp (signature)
References:
Ebuild questions
-- Brett I. Holcomb
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Ebuild questions
Next by thread:
Ebuild questions
Previous by date:
Readme files for portage (was: A nice idea to improve portage)
Next by date:
Re: Readme files for portage (was: A nice idea to improve portage)


Updated Jun 17, 2009

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.