[Lumiera] Installing on Wheezy - libgdl-lum-dev doesn't exist

[Ichthyostega]

Hello...

thanks for trying out our development snapshot. Unfortunately its
a bit outdated, since I didn't do any rebuilds of the binary packages
for quite some time. This process is still manual, and there wheren't
any user visible changes to the GUI recently.

Anyway, thanks for the reminder ;-)
We need to keep up with the general evolution of the linux distros
and try to rebuild it on a regular base. As the number in "libgdl-#-dev"
tells you, probably there had been some evolution in the API. I have
no idea yet if these changes are relevant for us, or if our build
would work with libgdl-3 instead of libgdl-1

Am 30.07.2012 07:32, schrieb Rodrigo Rodriguez:
> I've saw in a message on this same list [2] that that package isn't anymore 
> needed in Squeeze/Wheezy. In it's place, it's recommended to use 
> libgdl-1-dev.

Yes, indeed. Some years ago, we did some improvements to lib-GDL, which
where then picked up by the upstream developers. The "libgdl-lum" package
was just an interims solution until this happened.

> So the question is how can't I make that lumiera depends in libgdl-3-dev and 
> not in libgdl-lum-dev

Basically, there are two steps to make this happen:

1) change the actual build to pick up the newer libgdl and find out
   if this works. Maybe fix our source to comply to the new API.

2) change the debian package definition to include libgdl-3-dev as an
   alternate solution

> I've tried to force the libgdl package to version 1 (libgdl-1-dev) but the 
> system doesn't let me to do it.

Better not to force that in, since other applications also depend on libgdl.
Rather, we should try to make Lumiera compliant to the new situation.
I'll have a more close look into this issue this evening.

If you feel like experimenting (and since you've likely installed already
all the other dependencies), you could try to start with 1) by just changing
the definition in the Buildsystem. You'll find those in the file

admin/scons/Platform.py

Of course, after doing such changes in the build tree, you'd start the
build directly (like when just building from sources), and not the "debian way"
(the latter wouldn't work, since we've not yet done step (2) )

Regards,
Hermann V
(aka Ichthyo)