| 1 |
chrome://messenger/locale/messengercompose/composeMsgs.properties: |
| 2 |
> On 4 March 2010 23:34, Dale<rdalek1967@×××××.com> wrote: |
| 3 |
> [...] |
| 4 |
> |
| 5 |
>>> What it does not fix is the case of users who enable both cairo and |
| 6 |
>>> cups useflags on a system where neither gtk+ nor cups is present |
| 7 |
>>> yet. [...] |
| 8 |
>>> |
| 9 |
>> In the other post, I explained how this will not fix this at all. |
| 10 |
>> |
| 11 |
> So we agree there. You did not seem to grasp the following part: |
| 12 |
> |
| 13 |
> |
| 14 |
>>> But this issue can be discussed separately from whether cups |
| 15 |
>>> should be enabled in profiles. |
| 16 |
>>> |
| 17 |
> Cheers, |
| 18 |
> |
| 19 |
|
| 20 |
Actually, it is the problem. You want to remove cups to solve the |
| 21 |
problem of circular dependencies. How can you discuss one without the |
| 22 |
other? To say that you want to fix a problem that is not fixed just |
| 23 |
doesn't make sense. The problem, whether you remove cups or not, is |
| 24 |
still there. As soon as a user adds cups, you have changed nothing at |
| 25 |
all. The only difference is you get to blame the user for "creating" |
| 26 |
the problem by adding cups. |
| 27 |
|
| 28 |
It seems to me that the problem was created by splitting popular and now |
| 29 |
you need yet another fix. There needs to be a better way to do this. |
| 30 |
Fixing a fix, then fixing another fix and so on is not going to work. |
| 31 |
This is like running in circles. It gets you nowhere. |
| 32 |
|
| 33 |
Dale |
| 34 |
|
| 35 |
:-) :-) |
Archives