From: Geert Bevin <gbevin@theleaf.be>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Using new (masked) qt-x11-3.0.0 ebuild
Date: 19 Nov 2001 14:46:52 +0100 [thread overview]
Message-ID: <1006177612.23697.18.camel@willow> (raw)
In-Reply-To: <0GN100FBRUX14V@mxout2.netvision.net.il>
> Hm. Sounds intimidating :-) I suppose I'll remove the patch for now. BTW I've
> put a similar patch into the qt-2.3.2 ebuild, what do you think of that? I
I don't think that with qt2 this can be a problem since it doesn't use
tmake or qmake globally while qt3 ships with qmake as its default build
system.
> don't much mind what I do with the qt-3.0 ebuild, because you're almost
> certainly the only one who's using it right now.
>
> > Yes, the font problems are not due to your doing, but I would definately
> > add the -no-xft switch until trolltech resolves this matter. Using xft
> > everything really looks horrible and imho unusable. This might then
> > again be removed when a next release of qt3 fixes the problem.
> You're right; I'll do that.
Great !
> > Also
> > don't forget to update the 45qt-x11-3.0.0 file to use
> > /usr/lib/qt-x11-free-3.0.0 instead of /usr/lib/qt-x11-3.0.0.
> I've upated the ebuild to install into /usr/lib/qt-x11-3.0.0, so that the
> 45... file is correct.
--
Geert Bevin
the Leaf sprl/bvba
"Use what you need" Pierre Theunisstraat 1/47
http://www.theleaf.be 1030 Brussels
gbevin@theleaf.be Tel & Fax +32 2 241 19 98
prev parent reply other threads:[~2001-11-19 13:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 14:38 [gentoo-dev] Using new (masked) qt-x11-3.0.0 ebuild Dan Armak
2001-11-19 10:46 ` Geert Bevin
2001-11-19 11:14 ` Mikael Hallendal
2001-11-19 11:20 ` Geert Bevin
2001-11-19 11:46 ` Mikael Hallendal
2001-11-19 12:08 ` Geert Bevin
2001-11-19 13:11 ` Dan Armak
2001-11-19 13:25 ` Geert Bevin
2001-11-19 13:32 ` Dan Armak
2001-11-19 13:46 ` Geert Bevin [this message]
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=1006177612.23697.18.camel@willow \
--to=gbevin@theleaf.be \
--cc=gentoo-dev@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