On 12 July 2012 21:51, Ian Stakenvicius a...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/07/12 07:41 AM, Ben de Groot wrote:
On 12 July 2012 17:52, Rich Freeman ri...@gentoo.org wrote:
On Thu, Jul 12, 2012 at 12:17 AM, Ben de Groot
yng...@gentoo.org wrote:
On Thu, Jul 12, 2012 at 12:17 AM, Ben de Groot yng...@gentoo.org wrote:
Actually, there is another workable solution, and that is to set
USE=-gstreamer -icu for qt-webkit.
Currently we enable gstreamer by default in the ebuild (as it
is used for HTML5 audio/video, which is expected
On 12 July 2012 17:52, Rich Freeman ri...@gentoo.org wrote:
On Thu, Jul 12, 2012 at 12:17 AM, Ben de Groot yng...@gentoo.org wrote:
Actually, there is another workable solution, and that is to set
USE=-gstreamer -icu for qt-webkit.
Currently we enable gstreamer by default in the ebuild (as it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/07/12 12:17 AM, Ben de Groot wrote:
On 12 July 2012 06:51, Zac Medico zmed...@gentoo.org wrote:
Here's another related bug report, specifically about the solving
the libxml2/qt-webkit/chromium conflict:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/07/12 07:41 AM, Ben de Groot wrote:
On 12 July 2012 17:52, Rich Freeman ri...@gentoo.org wrote:
On Thu, Jul 12, 2012 at 12:17 AM, Ben de Groot
yng...@gentoo.org wrote:
Actually, there is another workable solution, and that is to
set
On 07/09/2012 06:05 PM, Zac Medico wrote:
On 07/09/2012 05:58 PM, Zac Medico wrote:
On 07/09/2012 05:42 PM, Rich Freeman wrote:
On Mon, Jul 9, 2012 at 10:56 AM, Rich Freeman ri...@gentoo.org wrote:
I'll test it out on a fresh install, but that will take a number of
hours
If I install
On 12 July 2012 06:51, Zac Medico zmed...@gentoo.org wrote:
Here's another related bug report, specifically about the solving the
libxml2/qt-webkit/chromium conflict:
https://bugs.gentoo.org/show_bug.cgi?id=426222
--
Actually, there is another workable solution, and that is to set
On 10 July 2012 09:41, Zac Medico zmed...@gentoo.org wrote:
On 07/09/2012 06:11 PM, Rich Freeman wrote:
So, seems like there is still room for improvement...
Aside from the obvious need to improve the portage behavior, we might
also want to consider enabling USE=icu by default in the profile.
On 10 July 2012 11:03, Rich Freeman ri...@gentoo.org wrote:
Yup, this issue hit anybody who has qt-webkit and chromium installed.
I wouldn't be surprised if that is half of the entire userbase.
I would be.
We ran into another confusing icu-related issue with qt-core a few
weeks ago (bug
On Tue, Jul 10, 2012 at 3:25 AM, Ben de Groot yng...@gentoo.org wrote:
On 10 July 2012 11:03, Rich Freeman ri...@gentoo.org wrote:
You keep saying that, but do you have any actual data to back up
that claim? There is no doubt that Chromium is a mainstream and
popular package, but I doubt if
On Tue, Jul 10, 2012 at 7:18 AM, Rich Freeman ri...@gentoo.org wrote:
On Tue, Jul 10, 2012 at 3:25 AM, Ben de Groot yng...@gentoo.org wrote:
On 10 July 2012 11:03, Rich Freeman ri...@gentoo.org wrote:
You keep saying that, but do you have any actual data to back up
that claim? There is no
After a little discussion in bug 425016 [1], I did an experiment.
I created a fresh Gentoo install, set the profile to desktop/kde, and
tried to emerge chromium and kde-meta.
The immediate response was for portage to suggest setting -u and -N
due to conflicts.
So, I tried emerge -puDNv
Rich Freeman wrote:
It also seems like the current portage output is giving the user some
contradictory and counterproductive advice. It seems like there are
really only two possible choices
1. The user could choose to not install chromium.
2. The user could enable icu for qt-webkit.
Do
On Mon, Jul 9, 2012 at 10:11 AM, Peter Stuge pe...@stuge.se wrote:
Rich Freeman wrote:
It also seems like the current portage output is giving the user some
contradictory and counterproductive advice. It seems like there are
really only two possible choices
1. The user could choose to not
On Mon, Jul 9, 2012 at 10:56 AM, Rich Freeman ri...@gentoo.org wrote:
On Mon, Jul 9, 2012 at 10:11 AM, Peter Stuge pe...@stuge.se wrote:
Rich Freeman wrote:
It also seems like the current portage output is giving the user some
contradictory and counterproductive advice. It seems like there
On Mon, Jul 9, 2012 at 11:04 AM, Michael Mol mike...@gmail.com wrote:
It shouldn't require *too* much modification to automate what you're
trying to test. I intend to modify it to work in chroot environments,
as a prelude to some build-related bug reports I'm sitting on.
Thanks - seems useful
On Mon, Jul 9, 2012 at 6:41 PM, Rich Freeman ri...@gentoo.org wrote:
Thanks - seems useful in general. Not sure I'll use it for this - a
chroot should be adequate to test this (I don't intend to actually run
KDE), and is much more efficient with CPU/RAM/etc.
Liberté Linux build scripts do a
On 07/09/2012 07:02 AM, Rich Freeman wrote:
Is there any way for portage to figure out that one of those is the
eventual outcome, and then direct the user to the minimal changes to
accomplish either?
You could try a larger emerge --backtrack setting. If it doesn't settle
on a sensible
On Mon, Jul 9, 2012 at 10:56 AM, Rich Freeman ri...@gentoo.org wrote:
I'll test it out on a fresh install, but that will take a number of
hours
If I install chromium first, I get the following messages when I try
to install kde-meta:
The following USE changes are necessary to proceed:
On 07/09/2012 05:42 PM, Rich Freeman wrote:
On Mon, Jul 9, 2012 at 10:56 AM, Rich Freeman ri...@gentoo.org wrote:
I'll test it out on a fresh install, but that will take a number of
hours
If I install chromium first, I get the following messages when I try
to install kde-meta:
The
On 07/09/2012 05:58 PM, Zac Medico wrote:
On 07/09/2012 05:42 PM, Rich Freeman wrote:
On Mon, Jul 9, 2012 at 10:56 AM, Rich Freeman ri...@gentoo.org wrote:
I'll test it out on a fresh install, but that will take a number of
hours
If I install chromium first, I get the following messages when
On Mon, Jul 9, 2012 at 8:58 PM, Zac Medico zmed...@gentoo.org wrote:
Not unless the --complete-graph option is enabled. What I'd like to do
is to automatically enable --complete-graph mode whenever the USE of an
installed package would change. It would be like that
--complete-graph-if-new-ver
On 07/09/2012 06:11 PM, Rich Freeman wrote:
On Mon, Jul 9, 2012 at 8:58 PM, Zac Medico zmed...@gentoo.org wrote:
Not unless the --complete-graph option is enabled. What I'd like to do
is to automatically enable --complete-graph mode whenever the USE of an
installed package would change. It
On Mon, 2012-07-09 at 10:56 -0400, Rich Freeman wrote:
On Mon, Jul 9, 2012 at 10:11 AM, Peter Stuge pe...@stuge.se wrote:
Rich Freeman wrote:
I don't have a copy of the message but when I got the update to
qt-webkit the message was fairly cryptic when it added the !icu?
dependency on
On Mon, Jul 9, 2012 at 10:22 PM, Brian Dolbec dol...@gentoo.org wrote:
There have already been users on the forums with that very confusion of
what to do with the cryptic [!icu?]. And there are currently many
forum threads involving the icu use flag, qt-webkit,...
Yup, this issue hit anybody
25 matches
Mail list logo
