[gentoo-user] qt blocks, poppler, etc.

[gentoo-user] qt blocks, poppler, etc.

[Alan E. Davis]

I am trying to install cb2bib from an overlay.  The ebuild is on
gentoo bugs.  On this machine, over time, I have gotten qt to settle
down, but now it's a mess.   I have tried to install some dependencies
with emerge -1 , but since I have too little understanding of that
issue, didn't do that for all.  Now qt-core has downgraded.

After installing (emerge -1) apps-text/poppler, then dev-libs/poppler
0.10.7 installed ok.  So I'm starting to understand how that works.
Can I also install x11-libs/qt-core-4.5.1 by oneshot, and then install
x11-libs/4.5.2?

This cyclical bunch of blocks has hit me many, many times, and I was
glad to discover that at least part of the problem was surmountable.

Alan Davis

 "...can the human soul be glimpsed through a microscope? Maybe, but
you'd definitely need one of those very good ones with two eyepieces."

    -- Woody Allen, quoted by B. A. Palevitz

Re: [gentoo-user] qt blocks, poppler, etc.

[Alan McKinnon]

On Sunday 05 July 2009 04:14:46 Alan E. Davis wrote:
> I am trying to install cb2bib from an overlay.  The ebuild is on
> gentoo bugs.  On this machine, over time, I have gotten qt to settle
> down, but now it's a mess.   I have tried to install some dependencies
> with emerge -1 , but since I have too little understanding of that
> issue, didn't do that for all.  Now qt-core has downgraded.
>
> After installing (emerge -1) apps-text/poppler, then dev-libs/poppler
> 0.10.7 installed ok.  So I'm starting to understand how that works.
> Can I also install x11-libs/qt-core-4.5.1 by oneshot, and then install
> x11-libs/4.5.2?
>
> This cyclical bunch of blocks has hit me many, many times, and I was
> glad to discover that at least part of the problem was surmountable.

First, unmask portage. The maintainer masked the 2.2_rc versions so that 
2.1.6* could get more testing. portage-2.2 can automatically resolve those 
blockers so you don't have to.

All those packages you mention are libs. You should never have to merge them 
manually, you should never have them in world - that's just asking for 
trouble. Remove them from world if they are there.

Tip: When you need support with blockers, always post the relevant emerge 
output and don't try to guess. This usually gets you an answer. Not posting 
the output gets you ignored, or a request to post the output. Either way, you 
should just post the output.


-- 
alan dot mckinnon at gmail dot com

[gentoo-user] Re: qt blocks, poppler, etc.

[ABCD]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alan McKinnon wrote:
> First, unmask portage. The maintainer masked the 2.2_rc versions so that
> 2.1.6* could get more testing. portage-2.2 can automatically resolve those
> blockers so you don't have to.

Actually, the latest 2.1.6.* versions contain the same auto-resolution for 
blockers that 2.2_rc* does, as the only difference between 2.1.6.* and 
2.2_rc* is that 2.2_rc* has support for sets and preserved-libs: everything 
else has been backported (actually, the 2.1.6 codebase was forked off of 
2.2, then the support for those two features was removed).

- -- 
ABCD
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)

iEYEARECAAYFAkpSu/cACgkQOypDUo0oQOqANQCfc5ePxReiIU79FXXUuOCLcvuK
DmoAoMA7/fba56fTha1bM9z0US4sRe6I
=2bTT
-----END PGP SIGNATURE-----