Only while llvm-3.5 stays in sid, and even for that case it's not a good policy. We can do it for the good of the users for sometime. Maybe gambas developer will update the library in the meantime. If you agree I can do it, if not the only solution is disabling llvm component from being built in the packaging.
2016-01-07 3:52 GMT+01:00 Ian Haywood <[email protected]>: > On Wed, Jan 6, 2016 at 9:47 PM, Gianfranco Costamagna > <[email protected]> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA256 > > > > control: forwarded -1 http://gambaswiki.org/bugtracker/edit?object=BUG.8 > > 35 > > > > Hi, unfortunately the bug report clearly shows that the features used > > are not compatible with recent llvm > > > > "LLVM 3.6 decided to replace their old JIT API by a new incompatible > > one, and so broke programs like Gambas that relied on them. > > There is no solution at the moment." > > > > so, since we don't know how to patch, and the component is optional I > > think I'll leave the current status quo, and maybe disable llvm on > > gambas if you eventually want to remove it from Debian. > generally when a project radically changes its API, the old version is > maintained for > some time (often years, think python 2.x and the old Linux kernels) > llvm-3.5 is still an available package in stretch and jessie, wouldn't > it be possible to have a specific dependency on llvm-3.5, until > upstream point gb.jit to 3.6? > > Ian > > _______________________________________________ > Pkg-gambas-devel mailing list > [email protected] > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-gambas-devel >
