Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 458202 - games-simulation/flightgear version bump to 2.10.0
Summary: games-simulation/flightgear version bump to 2.10.0
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Games (show other bugs)
Hardware: All Linux
: Normal minor (vote)
Assignee: Maciej Mrozowski
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-19 00:06 UTC by Christian Schmitt
Modified: 2013-02-20 21:43 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
ebuild patch for flightgear 2.10 (flightgear-2.8_2.10.patch,2.15 KB, patch)
2013-02-19 00:06 UTC, Christian Schmitt
Details | Diff
ebuild patch for simgear 2.10 (simgear-2.8_2.10.patch,1.01 KB, patch)
2013-02-19 00:07 UTC, Christian Schmitt
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Schmitt 2013-02-19 00:06:06 UTC
Created attachment 339322 [details, diff]
ebuild patch for flightgear 2.10

The following 2 patches bump games-simulation/flightgear and dev-games/simgear to version 2.10.0.

Reavertm: if you could explain what the remark in the flightgear ebuild means:
# Most entries below are just buildsystem bugs (deps unconditionally
# inherited from static version of simgear)
I'd like to help fixing this upstream. simgear and flightgear can be compiled with dynamic linking.
Comment 1 Christian Schmitt 2013-02-19 00:07:18 UTC
Created attachment 339324 [details, diff]
ebuild patch for simgear 2.10
Comment 2 Maciej Mrozowski gentoo-dev 2013-02-20 21:43:54 UTC
(In reply to comment #0)
Reavertm: if you could explain what the remark in the flightgear ebuild
> means:
> # Most entries below are just buildsystem bugs (deps unconditionally
> # inherited from static version of simgear)
> I'd like to help fixing this upstream. simgear and flightgear can be
> compiled with dynamic linking.

If you want to link flightgear against static simgear, you need to provide all simgear link deps (so you need to look for all libs that are required by simgear when linking shared simgear).
When linking against shared simgear, all simgear link deps are expected to be already provided by this shared simgear so there's no need to look for them in flightgear buildsystem. Therefore all those 'implicit deps' should be only searched in flightgear buildsystem when SHARED_SIMGEAR=OFF

Those are actual explicit linking dependencies of all binaries generated by games-simulation/flightgear package (output of dynlink-scanner from kde-testing repo) :

app-emulation/emul-linux-x86-baselibs-20121202 (false positive)
app-emulation/emul-linux-x86-opengl-20121202-r1 (false positive)
app-emulation/emul-linux-x86-xlibs-20121202 (false positive)
dev-db/sqlite-3.7.14.1
dev-games/openscenegraph-3.0.1-r1
dev-games/simgear-2.10.0
media-libs/freeglut-2.8.0-r1
media-libs/glu-9.0.0
media-libs/libpng-1.5.13-r1
media-libs/mesa-9.0.1 (read this as libGL.so dep)
sys-devel/gcc-4.6.3 (libstdc++)
sys-fs/udev-197-r8
sys-libs/glibc-2.15-r3
sys-libs/zlib-1.2.7
x11-drivers/nvidia-drivers-304.64 (read this as libGL.so dep)
x11-libs/libX11-1.5.0

If you compare this with ebuild dependencies (some of which I listed as 'bugs'):

>=dev-libs/boost-1.44
media-libs/openal
>=media-libs/plib-1.8.5
jpeg? ( virtual/jpeg )
subversion? (
	dev-libs/apr
	dev-vcs/subversion
)

boost is template only and it is probably actually needed in flightgear so it's likely fine. Checking for openal however is not needed most likely in flightgear when building with shared simgear. Plib is provided in Gentoo as static-only lib so it's fine that it's here. jpeg is likely not needed, the same with subversion/apr (no flightgear binary links to them).