chrome://messenger/locale/messengercompose/composeMsgs.properties:
On 03/03/2010 09:41 PM, Dale wrote:
So in the situation above, removing cups doesn't help any? The user
would still have to work around the dependency problem. Is there not a
better way to handle this?
Agreed that there should be better ways of handling things.
However, at the very least if somebody follows the instructions in the
Gentoo Handbook to the letter, they shouldn't end up staring at an
error message. A completely scripted install using any
non-experimental profile should "just work."
So, removing the use flag should probably be done at least in the
interim.
That said, I do agree that we need to try to avoid this circular
dependency in the first place. It is kind of silly that you can't
even do an emerge -u world right out of a stage3 using a fairly common
set of use flags and get a working system.
I only raised the point in case someone could come up with a better long
term solution. It may be that this is the only way right now. However,
it may be that someone will consider this that actually sits and writes
the code for portage or decides how dependencies are calculated. Maybe
a better way will present itself in the future. A good solution for
most of the blocks was found so this will be dealt with at some point
with a long term plan.
Now watch some geek find a really simple solution next week. ;-)
Dale
:-) :-)
