On Wed, 07 Jun 2006 11:53:10 -0400
dnlt0hn5ntzhbqkv51 <[EMAIL PROTECTED]> wrote:

> So IIUC,
> 
> 1. It is indeed using the qt 3 directory; which means 3.3.6.r-1
> libraries, and your patch will then still work!?

Yes.

>  I -guess- that I
> copy the "edit" notes from your bugzilla patch, insert it into a file
> named "qt-3.3.6-r1-dirty-ssp.patch"; put that into  
> /usr/portage/x11-libs/qt/files, and then reemerge qt!? (I just
> noticed that my first attempt at this was deleted - I guess by
> portage - do I have to put the name of this patch into some sort of
> manifest?)

It's a little more complex than that; you need to set up an overlay
(look for docs on www.gentoo.org), add the patch to the files
directory, modify the ebuild to include the patch in src_unpack(),
rebuild the digest, then emerge again.

An easier way to do it as a one-off process is to:

first save Andre's patch from bug #133301 to somewhere

# ebuild /usr/portage/x11-libs/qt/qt-3.3.6-r1.ebuild unpack
# cd /var/tmp/portage/qt-3.3.6-r1/work/qt-x11-free-3.3.6
# patch -p1 < [patch saved from bug]
# cd
# ebuild  /usr/portage/x11-libs/qt/qt-3.3.6-r1.ebuild merge

just note that if you emerge qt-3.3.6-r1 again later, the change will
be lost - but you're not likely to do that soon.

> 2. If I have the 4.1.2 qt version, why are the 3x libraries still
> around?

Because you still have lots of stuff built that needs it - if merging
qt4 deleted qt3, everything you have that links to qt3 (i.e. all
of KDE!) would fail to run because qt3 would be missing.

> 3. (IIRC, I recompiled KDE* after installing the new QT - yet KDE
> still uses 3.)

The version of qt used by kde-3.5 is qt3 - it specifically links to
qt3, rather than to "latest version".

> > No...  Are you sure it's using qt-4?  qt major versions are slotted
> > and from qt3 to qt4 the library names have changed.
> 
> 4. What does "slotted" mean, please? (webopedia and google didn't
> help :-( )

It just means you can have more than one version of a package installed
at the same time.

> > Report any findings on the same bug.
> >
> >> TIA (newbie)
> >
> >
> 
> Thanks AGAIN!!! newbie


-- 
Kevin F. Quinn

Attachment: signature.asc
Description: PGP signature

Reply via email to