To install it, add the overlay (using layman or PORTDIR_OVERLAY) and unmask qt-4.7_beta1 by copying or linking the keywords file we provide in your /etc/portage/package.unmask/ folder.

ln -s /path/to/qting-edge/Documentation/package.keywords/qt-4.7 /etc/portage/package.unmask/

# IF YOU USE A package.unmask FILE, run the following INSTEAD
cat /path/to/qting-edge/Documentation/package.keywords/qt-4.7 >> /etc/portage/package.unmask


then update your world:

emerge -avDuN world

if you only want to update Qt, run

emerge -av1 $(eix -I --only-names x11-libs/qt-)

Please report any ebuild-related bugs you find in our bugzilla, prefixed with [qting-edge] in the summary!

Enjoy

layman -d kde-testing; layman -L; layman -a kde;

In other news,

Qt 4.6.0 final was released by Nokia yesterday. You’ll find ebuilds in portage’s ~testing. If you’re using stable and want to try it out, make sure you keyword ALL the ebuilds, or you might get ugly blocks A keyword file is available in qting-edge.

Upgrading world is the recommended way to go to avoid B blocks. If you don’t want to upgrade world, make sure your upgrade command includes all installed Qt modules or you will get blocks.

emerge -av1 $(qlist -IC x11-libs/qt\-)

Remember that “b” (lowercase b) blocks are automatically resolved by portage, just remove --pretend and proceed with the upgrade.

For those wondering, KDE 4 works fine with Qt 4.6

If you’re upgrading Qt from a previous version and your Qt apps misbehave, you should rebuild everything depending on Qt:

emerge -av1 $(for i in $(qlist -IC x11-libs/qt-); do equery -q d $i | grep -v 'x11-libs/qt-' | sed "s/^/=/"; done)

KDE 4.3.4 was also released yesterday, ebuilds are available in portage as usual

Lots of stuff to build, have fun!

But there’s a catch.

4.6.0_rc1 is not binary compatible with 4.6.0_beta1. [1]
This means that if you’re upgrading from 4.6.0_beta1 you have to rebuild every single app depending on qt-*, or they won’t start at all. This obviously includes all of KDE 4.

You can get portage to do that by using a command like this:
*update* it seems some shells didn’t like the old command, so I’ve updated it:

emerge -av1 $(for i in $(qlist -IC x11-libs/qt-); do equery -q d $i | grep -v 'x11-libs/qt-' | sed "s/^/=/"; done)

Note that this command assumes your system is up-to-date. If some installed packages don’t have ebuilds available for their version anymore, you’ll have to resolve that manually (probably by removing them and rerunning the command).

You’ll find equery in app-portage/gentoolkit and qlist in app-portage/portage-utils.

You don’t need to do this if you’re upgrading from Qt 4.5.3 (although you should). You’ll also be safe if you upgrade from 4.5.3 to 4.6.0 final when the time comes.

Portage will warn you about this when you upgrade qt-core to 4.6.0_rc1:

* Messages for package x11-libs/qt-core-4.6.0_rc1:

*
* Binary compatibility broke between 4.6.0_beta1 and 4.6.0_rc1.
* If you are upgrading from 4.6.0_beta1, you’ll have to
* re-emerge everything that depends on Qt.
* Use the following command:
*
* emerge -av1 $(for pkg in $(equery -q d \
* $(qlist -IC x11-libs/qt-) | grep -v “x11-libs/qt-” |
* sort -u); do echo “=$pkg”; done)
*
* YOU’VE BEEN WARNED
*

But users (my user side as well :p) tend to ignore ewarns from time to time

Happy rebuilding!

[1] http://labs.trolltech.com/blogs/2009/11/12/bc-break-in-46-against-previous-46/

They also created two new branches, master-stable and 4.6-stable. Commits pushed to those branches are tested in Nokia’s testing farms, ensuring that they’ll always build.

The Gentoo Qt team provides various live Qt ebuilds in our official overlay, qting-edge [1]. These ebuilds now include x11-libs/qt-*-4.6.9999, building code from the 4.6 Qt branch, as well as a new USE flag called stable-branch, available (and enabled by default) in 4.6.9999 and 4.9999. This USE flag enables/disables the use of the stable branches, allowing you to choose between last-minute code VS tested, known to compile code.

Either way, its bleeding edge!

If you need help, leave a comment or visit us @ Freenode IRC, #gentoo-kde

[1] to install qting-edge, make sure you have layman installed and configured, then run layman -a qting-edge.

UPDATE: All <qt-*-4.5.3:4 ebuilds were removed on Nov 11th, 2009, so this problem is now fixed

So…… you’re trying to emerge kde 4 on your fresh ~ gentoo installation but strange blocks show up… stuff like

[blocks B ] >x11-libs/qt-opengl-4.5.1-r9999 (">x11-libs/qt-opengl-4.5.1-r9999" is blocking x11-libs/qt-gui-4.5.1-r2, x11-libs/qt-dbus-4.5.1)
[blocks B ] >x11-libs/qt-webkit-4.5.1-r9999 (">x11-libs/qt-webkit-4.5.1-r9999" is blocking x11-libs/qt-gui-4.5.1-r2, x11-libs/qt-dbus-4.5.1)
[blocks B ] >x11-libs/qt-svg-4.5.1-r9999 (">x11-libs/qt-svg-4.5.1-r9999" is blocking x11-libs/qt-gui-4.5.1-r2, x11-libs/qt-dbus-4.5.1)
[blocks B ] >x11-libs/qt-core-4.5.1-r9999 (">x11-libs/qt-core-4.5.1-r9999" is blocking x11-libs/qt-gui-4.5.1-r2, x11-libs/qt-dbus-4.5.1)
[blocks B ] >x11-libs/qt-qt3support-4.5.1-r9999 (">x11-libs/qt-qt3support-4.5.1-r9999" is blocking x11-libs/qt-gui-4.5.1-r2, x11-libs/qt-dbus-4.5.1)
[blocks B ]
[blocks B ] x11-libs/qt-sql-4.5.1-r9999 (">x11-libs/qt-sql-4.5.1-r9999" is blocking x11-libs/qt-gui-4.5.1-r2, x11-libs/qt-dbus-4.5.1)
[blocks B ] >x11-libs/qt-script-4.5.1-r9999 (">x11-libs/qt-script-4.5.1-r9999" is blocking x11-libs/qt-gui-4.5.1-r2, x11-libs/qt-dbus-4.5.1)
[blocks B ] >x11-libs/qt-test-4.5.1-r9999 (">x11-libs/qt-test-4.5.1-r9999" is blocking x11-libs/qt-gui-4.5.1-r2, x11-libs/qt-dbus-4.5.1)

All this is happening because of recent changes to gentoo’s Qt ebuilds. In Qt Team’s last meeting it was decided to make most USE flags disabled by default, to allow the user to choose which ones he wants to enable, rather than disable.

However, in portage’s current state, the stable Qt packages (4.5.1 version) use the old USE flags with lots of them enabled by default.

Now comes the tricky part. KDE depends on qt-gui with dbus USE flag enabled. Normally, when portage sees that dependency, it checks your USE flags. If dbus is enabled, all is good. If not, it breaks with an error telling you to enable it.

In reality this never happens. Portage first checks qt-gui-4.5.2, which doesn’t have dbus enabled by default. No go. But wait, qt-gui-4.5.1 has it enabled and portage falls back to it. So now portage tries to mix all the other qt-*-4.5.2 packages with qt-gui-4.5.1 (and its 4.5.1 dependencies) and as I’ve mentioned before, this is not allowed.

Boom, blockers.

SOLUTION

Ok maybe you didn’t feel like reading all of the above, so I’ve titled this so you can find it easily

The solution to this problem is suprizingly easy.

Add “dbus” and “qt3support” to your make.conf USE (dbus can also go in package.keywords for qt-gui).

OR

Switch to the Desktop Profile.

Its that easy (thankfully)

WHY DID IT HAVE TO BREAK?

Thats a good question. The real reason this broke is because the stable version has +dbus (which we can’t change now cause its stable – too much hassle) and the testing version has -dbus (which is better since the idea is you get a package and “add” to it with USE flags). Since the Qt Team decided to go through with this change and Portage falls back to the older version without a warning, there’s nothing we can do about this, at least until a new Qt version goes stable with -dbus or portage’s behavior changes.

Thats all folks =] Questions welcome in the comment system below

[blocks B     ]  >x11-libs/qt-gui-4.4.2-r9999 (“>x11-libs/qt-gui-4.4.2-r9999″ is blocking x11-libs/qt-xmlpatterns-4.4.2, x11-libs/qt-script-4.4.2,
x11-libs/qt-dbus-4.4.2, x11-libs/qt-sql-4.4.2-r1, x11-libs/qt-qt3support-4.4.2, x11-libs/qt-svg-4.4.2, x11-libs/qt-test-4.4.2, x11-libs/qt-opengl-4.4.2,
x11-libs/qt-core-4.4.2-r2)

[blocks B     ]    <x11-libs/qt-gui-4.5.1 (“<x11-libs/qt-gui-4.5.1″ is blocking x11-libs/qt-opengl-4.5.1, x11-libs/qt-svg-4.5.1-r1, x11-libs/qt-script-4.5.1,
x11-libs/qt-dbus-4.5.1, x11-libs/qt-xmlpatterns-4.5.1, x11-libs/qt-test-4.5.1, x11-libs/qt-qt3support-4.5.1, x11-libs/qt-sql-4.5.1, x11-libs/qt-core-4.5.1)

this means that new Qt libraries are available and portage is trying to upgrade only *a part* of the ones you have installed.

this is bad because mixed versions of Qt packages (like qt-core-4.5.1 alongside qt-svg-4.4.2) can result in unexpected breakage.

unfortunately, at the moment this error is the only way we can prevent version mixing.

to get past the error, you can:

• emerge -avDuN world
  • updating world tells portage to upgrade all Qt packages in one run
• emerge -av1 `eix -I --only-names x11-libs/qt-`
  • if you don’t want to upgrade everything, you can use this command to upgrade all the installed Qt libraries

if you still have problems, don’t hesitate to comment and I’ll do my best to help