Bug 2543 - python-opengl needs a spec cleaning (switch BR from mesaglut-devel to freeglut-devel)
Summary: python-opengl needs a spec cleaning (switch BR from mesaglut-devel to freeglu...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: Junior_job
Depends on:
Blocks:
 
Reported: 2011-08-28 13:45 CEST by Philippe Didier
Modified: 2011-09-23 18:12 CEST (History)
2 users (show)

See Also:
Source RPM: python-opengl
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Philippe Didier 2011-08-28 13:45:56 CEST 
After some discussion on dev mailing list, in order to switch from GLUT
(mesaglut) to freeglut in cauldron : this package needs to have its spec file
modified and needs to be rebuilt with a modified BuilRequire .

see:
 https://bugs.mageia.org/show_bug.cgi?id=2412

It may be built with :

BuildRequire : freeglut-devel 
(the freeglut-devel package provides glut standard headers, and freeglut
headers : that means standard plus enhanced glut headers)

instead of BuildRequire mesaglut-devel or libmesaglut-devel


In a first step it may be possible to try to build it without any glut stuff 
(we discovered that some packages don't need mesaglut-devel anymore and 
a fortiori will not need freeglut-devel)
Philippe Didier 2011-08-28 13:46:42 CEST

CC: (none) => philippedidier

Philippe Didier 2011-08-28 14:31:08 CEST

CC: (none) => makowski.mageia

Manuel Hiebel 2011-08-28 15:16:52 CEST

Keywords: (none) => Junior_job

Jani Välimaa 2011-08-29 19:56:30 CEST

Summary: this package needs a spec cleaning (switch BR from mesaglut-devel to freeglut-devel) => python-opengl needs a spec cleaning (switch BR from mesaglut-devel to freeglut-devel)

Comment 1 Philippe Makowski 2011-09-23 18:12:00 CEST 
fixed http://svnweb.mageia.org/packages?view=revision&revision=147070

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.