From: taylanbayirli@gmail.com (Taylan Ulrich Bayırlı/Kammer)
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Patch Qt 5.4 for i686.
Date: Wed, 29 Apr 2015 22:25:07 +0200 [thread overview]
Message-ID: <87bni6el7g.fsf@taylan.uni.cx> (raw)
In-Reply-To: <87oam6g05q.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 29 Apr 2015 22:16:49 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver <mhw@netris.org> skribis:
>
>> Please, let's not do that. We should be moving in the other direction,
>> by using less, not more, of the unbelievably massive amount of bundled
>> stuff in Qt.
>
> Agreed.
>
>> If this "fix" is the really best we can hope for from upstream, then
>> let's do it this way instead: after unpacking Qt 5, make a copy of
>> glext.h from *our* system Mesa, apply the above patch to that copy, and
>> arrange for that patched copy to be found first in the include search
>> path during the Qt build. Then at least we will have only one copy of
>> Mesa in memory and only one copy of the Mesa source code to maintain
>> (for security fixes, fixes for non-Intel platforms, fixes for Guix,
>> etc).
>
> Sounds like a good plan.
>
>> Thanks again, Taylan, for working on this unpleasant task.
>
> Indeed, this is neither easy nor funny, but work in this area is
> definitely appreciated!
>
> Thanks,
> Ludo’.
Seems I left this thread dangling; I sent a new patch in a new thread on
the meanwhile. And it even seems to work this time. :-)
Taylan
prev parent reply other threads:[~2015-04-29 20:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 9:16 [PATCH] Patch Qt 5.4 for i686 Taylan Ulrich Bayırlı/Kammer
2015-04-24 19:07 ` Taylan Ulrich Bayırlı/Kammer
2015-04-25 5:17 ` Mark H Weaver
2015-04-29 20:16 ` Ludovic Courtès
2015-04-29 20:25 ` Taylan Ulrich Bayırlı/Kammer [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bni6el7g.fsf@taylan.uni.cx \
--to=taylanbayirli@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).