Gentoo Archives: gentoo-dev

From: Fernand Albarracin <fernand8@×××××××.fr>
To: gentoo-dev@g.o
Subject: [gentoo-dev] ebuild inconsistencies (was: Community driven meta distribution or only distribution)
Date: Tue, 29 Apr 2003 23:48:28
Message-Id: 20030429235437.GA8993@spirou.test-domain
1 Hi,
2
3 On Tue 29 Apr 2003 at 15:31:54 -0400, Grant Goodyear wrote:
4
5 > A good "reference" ebuild can be found by "man 5 ebuild".
6
7 Just checked it, and have few remarks.
8
9 Here is a part of the supplied sample ebuild :
10
11 src_compile() {
12 econf || die "could not configure"
13 emake || die "emake failed"
14 }
15
16 An here is the revelant documentation :
17
18 ...
19 *Note: There is no need to use '|| die' because
20 econf checks for you
21
22 ...
23 *Note: Be sure to use '|| die' constructs to
24 ensure emake success
25
26 1. The example should be updated.
27
28 src_compile() {
29 econf
30 emake || die "emake failed"
31 }
32
33 2. It might be a good idea to change emake so that it works just like
34 econf and einstall. What do you think ? Goal: get a simpler, more
35 consistent API.
36
37 Also right now econf is implemented as a function, and emake as a
38 program. Is there a good reason for this ? Sure, it does not really
39 matter from an ebuild writter point of view, it's more a "spring
40 cleanup" kind of suggestion.
41
42 Ok, enough for today :)
43
44 Fernand
45
46 --
47 gentoo-dev@g.o mailing list