public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Roy Wright <roy@wright.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: finding qt plugins?
Date: Tue, 30 Jun 2009 14:54:40 -0500	[thread overview]
Message-ID: <F2A6A968-0F81-4EBE-85CC-FD84F363E578@wright.org> (raw)
In-Reply-To: <4A4881C9.3070302@gmail.com>


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.

-------------------





  reply	other threads:[~2009-06-30 19:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29  5:04 [gentoo-user] finding qt plugins? Roy Wright
2009-06-29  5:21 ` Dale
2009-06-29  6:03   ` [gentoo-user] " Nikos Chantziaras
2009-06-29  8:18     ` Graham Murray
2009-06-29  8:56     ` Dale
2009-06-30 19:54       ` Roy Wright [this message]
2009-06-30 20:16         ` Paul Hartman
2009-06-30 21:41           ` Roy Wright
2009-06-30 22:26             ` Roy Wright
2009-07-01  5:29               ` Graham Murray
2009-07-01  5:42                 ` Roy Wright
2009-07-01  1:13         ` Dale
2009-06-29  6:11 ` Nikos Chantziaras
2009-06-29 14:47 ` [gentoo-user] " Paul Hartman
2009-07-01 16:25   ` Paul Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F2A6A968-0F81-4EBE-85CC-FD84F363E578@wright.org \
    --to=roy@wright.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox