Hello Etienne!
On Sat, Feb 15, 2014 at 10:10:58PM +0100, Etienne Millon wrote:
> Hi,
>
> Well, half a year is not so bad :-/ Sorry for hindering the removal.
>
> If I remember correctly, porting the current version to a recent vala
> compiler would require a non negligible amount of work (by the way, do
> you know if there is a porting guide for valac upgrades?). Upstream is
> working on a new version but has not released one yet.
I'm not an expert on vala myself and I'm not aware of a porting guide.
Usually I just google a particular problem and there most of the time
is someone else who has already solved a similar problem which you can
follow.
Yesterday I briefly looked into what it would take to port gmpc to
newer vala. At first I just had to change a function prototype where
bindings had changed from ...(out x, out y, ...) to
...(ref x, ref y, ...).
After that additional problems came up so I looked a bit at recent
upstream VCS history.... Looks like they haven't switched to newer
vala their either since they where still using the old ("out") function
prototype.
>
> The best course of action is probably to package a git snapshot and
> convince upstream to release before the freeze, as I'd like to provide
> a newer gmpc for jessie (including glyr support etc).
With latest upstream snapshot you'll also need the latest upstream
snapshot of libmpd, which has bumped SONAME (not ABI compatible) so
it'll need a transition in debian...
So this path is not very straight forward either unfortunately. :(
I understand it will take some work and require some time to get gmpc
ported to newer vala. I just wanted to make sure it's atleast on your
todo list and maybe with a bit of a priority because if/when gmpc
is the last thing that requires vala 0.16 we'll have to discuss how
to deal with the situation....
Regards,
Andreas Henriksson
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
