1 |
I'm wanting to use catalyst to make a safe build environment for a few |
2 |
boxes, intending on using the binaries generated there for the sole |
3 |
method of updating. |
4 |
|
5 |
Currently I'm having a hard time with, specifically, gtk+-2.8.19.ebuild |
6 |
... which has the following behavior: |
7 |
|
8 |
1. in pkg-setup, it checks to see if cairo was built with the X use |
9 |
flag, and die's if not. |
10 |
2. cairo is specified in RDEPEND, which is followed by DEPEND, which |
11 |
includes RDEPEND. |
12 |
3. cairo is *NOT* in the build list |
13 |
4. cairo is *NOT* in the pkg_cache |
14 |
5. the ebuild fails because of #1, due to #3 and #4. |
15 |
|
16 |
in addition to the above confusing behavior, catalyst *EXITS* at this |
17 |
point, though the tinderbox target is supposed to continue building on |
18 |
failures. |
19 |
|
20 |
n8 |
21 |
|
22 |
PS. I'm not sure what data is traditionally attached to this list, so |
23 |
I'll hold back on it for now, except for noting that I'm using portage i |
24 |
sync'd 2006-09-27, with i686 and some 500+ tinderbox/packages. |
25 |
|
26 |
|
27 |
|
28 |
|
29 |
--- |
30 |
[This E-mail was scanned for viruses by Quest Technology Group (http://www.quest-technology-group.com)] |
31 |
|
32 |
-- |
33 |
gentoo-catalyst@g.o mailing list |