Gentoo Archives: gentoo-dev

From: justin <jlec@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] RFC: emboss.eclass as replacement for embassy.eclass
Date: Wed, 16 Mar 2011 06:48:59
Message-Id: 4D805D2C.4020206@gentoo.org
In Reply to: Re: [gentoo-dev] RFC: emboss.eclass as replacement for embassy.eclass by "Tomáš Chvátal"
1 On 15/03/11 22:25, Tomáš Chvátal wrote:
2 > Dne 15.3.2011 21:51, justin napsal(a):
3 >> Donnie pointed out, that it might be clever to attach what I want to
4 >> have reviewed. So here it is.
5 >
6 >> justin
7 > EAPI CAN'T BE DEFINED IN ECLASS!
8 > this should be craved into stones :)
9
10 I didn't see this mentioned anywhere in the docs. But okay, this is fixable.
11
12 >
13 > Some whitespace is funny.
14
15 I love funny whitespaces.
16
17 >
18 > look on XFCONF_AUTORECONF or XORG_AUTORECONF variable, just create
19 > EBO_AUTORECONF with yes by default and handle it correctly.
20
21 Thanks for that hint. I will change it accordingly.
22
23 >
24 > i am seriously hurt by $(use_enable amd64 64)
25
26 Where is the problem? The purpose of the eclass is not to repeat the
27 same code 20 times. Why can't this be here?
28
29 >
30 > why are not those functions exported for embassy ebuild?
31
32 Just a Meta ebuild to install all modules (emabassy-*).
33
34 >
35 > Cheers
36 >
37 > Tom
38
39 thanks justin

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: [gentoo-dev] RFC: emboss.eclass as replacement for embassy.eclass "Tomáš Chvátal" <scarabeus@g.o>