On Fri, Jun 26, 2009 at 4:11 AM, Michael Schwendt <mschwendt@xxxxxxxxx> wrote:
It's "qt3" that alters $PATH via /etc/profile.d/qt.{c,}shOn Fri, 26 Jun 2009 03:05:41 -0500, King wrote:
> I found a very strange omission for the qt4-devel package. The path to
> qt4-devel binaries (/usr/lib/qt4/bin) isn't automatically added to $PATH
> like qt3's are.
> Additionally, when I removed the qt3-devel package, the path to qt3-devel
> binaries (/usr/lib/qt-3.3/bin) isn't automatically removed from the $PATH.
>
> Shouldn't these be fixed?
"qt" only puts symlinks into /usr/lib/qt4/bin that point to /usr/bin,
so the executables are found with default $PATH already.
What do you find "very strange" about it? Have you run into any source
tarball that fails with qt-devel/qt because it makes strange assumptions?
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
Yes I have. I was unable to build Mozilla with the cairo-qt option because it was unable to detect Qt4's moc. Even after uninstalling Qt3 and reinstalling Qt4, moc still was never detected. No, wait, Qt3's moc was detected but it caused problems building cairo-qt, so I uninstalled it and discovered that it wasn't able to detect Qt4's moc. I had to temporarily export /usr/lib/qt4/bin to $PATH to make it get detected.
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
