chrome://messenger/locale/messengercompose/composeMsgs.properties:
Hi,
On 2010-03-05 00:00 UTC Dale wrote:
chrome://messenger/locale/messengercompose/composeMsgs.properties:
On 5 March 2010 00:27, Dale<rdalek1...@gmail.com> wrote:
But this issue can be discussed separately from whether cups
should be enabled in profiles.
Actually, it is the problem. You want to remove cups to solve the
problem of circular dependencies.
What I wrote was:
What it fixes is (1) the circular dependency that people run into on a
fresh install and the default desktop profile, and (2) the default
dependency on cups that many users do not need.
But if you choose to ignore what I actually write, then I'd better stop
responding.
Good night,
You notice what I wrote? If I had to install Gentoo again, I would copy
or set my USE flags first then install. If I do that right after
unpacking the tarball, which is how it should be done, then you have
fixed nothing. The problem you claim to have fixed is not fixed at all.
Maybe it is not me that should stop responding?
Obviously, users who "re-install" Gentoo the way you do will have less
difficulties resolving a circular dependency than those who are just following
the guide and getting their first Gentoo experience.
Patrick.
Not quite. If a person reads the docs and other howto's, they will know
to set up the USE flags and other things in make.conf. Isn't the USE
flags one of Gentoo's strong points? It is one reason I chose Gentoo
after all. I have read where others say it as a strong point as well.
So, the same thing will most likely happen to anyone installing Gentoo.
Case in point, I also went here:
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=6
If you scroll down to section 2.3, that is where it tells you to select
your profile. Want to guess what is next? Yep, setting the USE flags.
So, chroot in, sync the tree, select the profile then add your USE
flags. So far, we are where we was several replies ago. Same problem
and that is following the official install guide. I wasn't looking at
the expert guide, that is the general user guide for newbies.
If this was some rarely used flag then maybe this would make a little
sense. This is cups. It's not something that is rarely used or that
someone even a little familiar with Linux wouldn't know to turn it on.
They may not know what cups stands for but they know it makes their
printer work.
I guess like with some other things, the devs can do it their way and
let that be the end of it. I just feel the best way is to find a long
term fix for this and other similar issues. If it is not done now, it
will just pile up until it is fixed. Just like the problem with
blocks. It got bad enough that someone had to find a way to fix it.
Someone did just that. I don't know who that person is but that was a
job well done. We need the same type of person to deal with this.
Dale
:-) :-)
