FS#37924 - [ogre] New dependency on gcc-go

Attached to Project: Community Packages
Opened by Philipp (hollunder) - Wednesday, 27 November 2013, 07:36 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 02 December 2013, 00:53 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Ogre now depends on gcc-go, but it is unclear why. As far as I know, ogre is still written in C++, not go.

Additional info:
* package version(s)
ogre 1.9.0-1
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Monday, 02 December 2013, 00:53 GMT
Reason for closing:  Fixed
Additional comments about closing:  ogre-1.9.0-2
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 27 November 2013, 09:52 GMT
You are correct, though this was currently the only way to package ogre. There is a packaging bug (https://bugs.archlinux.org/task/37928) in gcc-libs where libatomic is in gcc-go instead of in gcc-libs. I will remove this dependency after libatomic moves to gcc-libs in a week or so. Will keep this bug open till then.

Loading...