From: "José Fonseca" <j_r_fonseca@yahoo.co.uk>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Mesa >=3.5 masked!?
Date: Mon, 20 May 2002 14:29:36 +0100 [thread overview]
Message-ID: <20020520142936.E8474@localhost> (raw)
I noticed that Mesa >= 3.5 is masked but I don't understand why.
In package.mask says:
#mesa 3.5 apparently breaks source compatibilty with 3.4.2 and we should
#stay with 3.4.2 'cause so many apps depend on it. (drobbins, 26 Jan
2002)
#sad but true, we're stuck at 3.4.2.
#
#think we should try mesa 4.0.1 sometime, although including glu in the
xfree
#ebuild seems to have good results.
#azarah (29/01/2002)
I don't see how the first comment can be true as Mesa is an implementation
of the OpenGL standard which, besides of source compatibility, also has
binary compatibility within a platform. Mesa releases notes also don't
mention nothing like that.
Regarding the second comment I found the referring bug number 245. It says
that NVIDIA can't use the SGI libGLU.la 1.3 included in Mesa >=3.5. If so
then why is the same SGI libGLU 1.3 available trhu the sgi-oss-glu ebuild?
Stranger is that the "Nvidia OpenGL Configuration mini-HOWTO"
(http://www.tldp.org/HOWTO/mini/Nvidia-OpenGL-Configuration/) uses Mesa
4.0.1 in the tutorial, but on the other hand the author does state that
"not had time to test all the procedures"...
So it seems that there is quite a bit of misunderstanding. Is it mine or
should I fill in a bug report?
José Fonseca
next reply other threads:[~2002-05-20 13:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-20 13:29 José Fonseca [this message]
2002-05-20 21:14 ` [gentoo-dev] Mesa >=3.5 masked!? Martin Schlemmer
2002-05-20 22:32 ` José Fonseca
2002-05-21 13:28 ` Lars S. Jensen
2002-05-21 15:44 ` José Fonseca
2002-05-21 15:56 ` José Fonseca
2002-05-21 21:51 ` Martin Schlemmer
2002-05-21 23:13 ` José Fonseca
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=20020520142936.E8474@localhost \
--to=j_r_fonseca@yahoo.co.uk \
--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