On Jun 29, 2009, at 3:56 AM, Dale wrote:
Nikos Chantziaras wrote:
revdep-rebuild only resolves link-time errors, not runtime errors.
You need to observe yourself if something is broken and then rebuild
it manually; revdep-rebuild ain't gonna help in this case.
Sounds like Gentoo needs a new tool. Calling all geeks and nerds !!
Dale
Drum roll please...
http://github.com/royw/qt-rebuild
A couple of notes:
* if you run qt-rebuild --pretend, you should have only one build key.
if you have more than one, you really need to rebuild them.
* the build key does not contain the qt version. Instead it describes
the build environment.
So currently I don't see how to verify that all the plugins are built
to the
same qt API.
Here's the readme:
= qt-rebuild
This is a utility for gentoo (http://gentoo.org) linux.
When QT is upgraded, you may have to rebuild any QT plugins. This
utility
attempts to find and rebuild packages with QT plugins.
Here's the discussion thread:
http://archives.gentoo.org/gentoo-user/msg_d9357c6f26dec67492b794f8f66db29d.xml
== Installation
$ emerge ruby rubygems
$ sudo gem install royw-qt-rebuild --source http://gems.github.com
== Usage
$ qt-rebuild -h
OPTIONS
--version,-v
This version of qt-rebuild
--help,-h
Print usage.
--quiet,-q
Display error messages only.
--debug,-d
Display debug messages.
--set,-s
Output in portage's set format.
--nocolor,-C
Turn off colored output. (This option is also passed to
portage.)
--pretend,-p
Do a dry-run.
It is recommended to do a dry run first:
$ qt-rebuild -p
To create a set file:
$ qt-rebuild -s -p > /etc/portage/sets/qt-rebuild
== Copyright
Copyright (c) 2009 Roy Wright. See LICENSE for details.
-------------------
