1 |
On N, 2010-03-04 at 12:50 +0100, Ben de Groot wrote: |
2 |
> 2010/3/4 Dawid Węgliński <cla@g.o>: |
3 |
> > On Wednesday 03 March 2010 22:51:10 Ben de Groot wrote: |
4 |
> >> I'm not talking about selectively disabling cups. My proposal is |
5 |
> >> to no longer enable the cups useflag in the base profile. |
6 |
> > |
7 |
> > How is that going to fix circular dependency problem? What will you do if every |
8 |
> > user add cups to USE in make.conf? Say "we don't support cups turned on by |
9 |
> > default"? I hope no. Removing this flag from profile will not fix any problem but |
10 |
> > hide it. |
11 |
> |
12 |
> It will fix the "out of the box" circular dependency for people who |
13 |
> switch to a default desktop profile. This is the main problem we |
14 |
> need to solve now. |
15 |
|
16 |
The main problem to solve here is the circular dependency that you |
17 |
yourself introduced as a co-maintainer of poppler, by converting poppler |
18 |
to be monolithic. This from the outside looks like it was done to reduce |
19 |
your maintenance workload in the (possibly accidental) expense of users |
20 |
who are now getting circular dependencies in a fairly common setup. |
21 |
|
22 |
If cups should be enabled in the desktop profile or not is a completely |
23 |
different question. |
24 |
|
25 |
The correct solution here is to fix the core problem that is now |
26 |
happening - not to start removing common desktop needed USE flags from |
27 |
the desktop profiles to delay the correct fix for this circular |
28 |
dependency you guys have introduced for us. |
29 |
|
30 |
> Certain useflag and package combinations |
31 |
> will trigger a circular dep, that is a know occurrence in Gentoo. |
32 |
> But at least with a default configuration things should work out of |
33 |
> the box. For other configurations there are workarounds (in this |
34 |
> case: install gtk+ without cups, or poppler without cairo enabled |
35 |
> first). |
36 |
|
37 |
Circular dependencies shouldn't happen in any situation. I claim there |
38 |
is always a solution to avoid it. A different question is if the cost of |
39 |
the solution is acceptable compared to the problems it causes. I believe |
40 |
an inconvenience for the poppler maintainers is completely justified |
41 |
here for the benefit of users in the form of properly split packages, |
42 |
considering how this affects a majority of desktop users (problem hidden |
43 |
by default or not). |
44 |
|
45 |
|
46 |
I'll later make sure there is a bug for fixing this circular dependency |
47 |
mess properly. I believe the only possible fix is to split poppler back |
48 |
to at least core, bindings and utils, as it seems to be a problem due to |
49 |
poppler-utils requirement by cups. It doesn't need poppler-glib, so |
50 |
utils and bindings being a separate package, as it always was before, |
51 |
would nicely solve it. |
52 |
|
53 |
|
54 |
-- |
55 |
Mart Raudsepp |
56 |
Gentoo Developer |
57 |
Mail: leio@g.o |
58 |
Weblog: http://blogs.gentoo.org/leio |