1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Iván Pérez Domínguez wrote: |
5 |
> Hi there. |
6 |
> |
7 |
> I just happend to emerge evince and, after half an hour got the |
8 |
> following error: |
9 |
> |
10 |
> |
11 |
> 18:07:32 (44.99 KB/s) - `/usr/portage/distfiles/evince-0.6.1.tar.bz2' |
12 |
> saved [1212271/1212271] |
13 |
> |
14 |
> * checking ebuild checksums ;-) ... |
15 |
> [ ok ] |
16 |
> * checking auxfile checksums ;-) ... |
17 |
> [ ok ] |
18 |
> * checking miscfile checksums ;-) ... |
19 |
> [ ok ] |
20 |
> * checking evince-0.6.1.tar.bz2 ;-) ... |
21 |
> [ ok ] |
22 |
> * Please re-emerge app-text/poppler-bindings with the gtk USE flag set |
23 |
> |
24 |
> !!! ERROR: app-text/evince-0.6.1 failed. |
25 |
> Call stack: |
26 |
> ebuild.sh, line 1626: Called dyn_setup |
27 |
> ebuild.sh, line 701: Called qa_call 'pkg_setup' |
28 |
> ebuild.sh, line 38: Called pkg_setup |
29 |
> evince-0.6.1.ebuild, line 67: Called die |
30 |
> |
31 |
> !!! poppler-bindings needs gtk flag set |
32 |
> !!! If you need support, post the topmost build error, and the call |
33 |
> stack if relevant. |
34 |
> |
35 |
> |
36 |
> I understand why this happend, and I know how to solve it. |
37 |
> |
38 |
> My point is: should the RDEPEND and DEPEND syntax in ebuilds be changed |
39 |
> so that this kind of problems can be detected before emerging? |
40 |
> |
41 |
> Here's an example. Imagine program A depends on B, and if A is built |
42 |
> with use flag "dvi", then it depends on C to be built with use flag |
43 |
> dvi2. The following could be A's DEPEND: |
44 |
> |
45 |
> DEPEND="dvi? ([dvi2 C]) |
46 |
> B" |
47 |
> |
48 |
> This is just an example, and I'm sure there's a different syntax that |
49 |
> could be more appropriate. |
50 |
> |
51 |
> What do you this of it? |
52 |
> |
53 |
> Is there any ongoing implementation to solve it in a different way? |
54 |
> |
55 |
> Cheers, |
56 |
> |
57 |
> Ivan. |
58 |
Ivan, from my personal experience I find your advice to be highly |
59 |
important. It would be beneficial to everyone if we knew the |
60 |
dependencies before emerging from portage.I highly suggest sending a |
61 |
message on gentoo-dev@g.o (confirm this). I really do support this. |
62 |
|
63 |
Best regards. |
64 |
|
65 |
Avaricen |
66 |
|
67 |
-----BEGIN PGP SIGNATURE----- |
68 |
Version: GnuPG v1.4.5 (GNU/Linux) |
69 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
70 |
|
71 |
iD8DBQFFq9oFQHQy/61tbpYRAiKGAJ4n+wmarim7SjQpG3PWEZaQXkUwAgCfZLz6 |
72 |
8Iig49rBTs/aCnbJpMGYXJ8= |
73 |
=zOBE |
74 |
-----END PGP SIGNATURE----- |
75 |
-- |
76 |
gentoo-user@g.o mailing list |