Re: Problems running autogen for Nemiver
- From: Dodji Seketeli <dodji seketeli org>
- To: The mailing list of the Nemiver project <nemiver-list gnome org>
- Subject: Re: Problems running autogen for Nemiver
- Date: Fri, 13 May 2011 13:11:27 +0200
Luca Bruno <lucab debian org> a écrit:
> I have not seen this either (on a Debian unstable).
> Plus, even adding the test-framework by hand the configure
> still succeeds (with the bare minimum build-dep).
Oh, Seemanta's issue is being triggered when he enables the automatic
tests. By default you don't have these activated, unless you either set
the NEMIVER_DEVEL=on environment variable prior to running
autogen.sh/configure, or you pass --enable-autotest to
autogen.sh/configure.
> Moreover, it looks like during last release cycle, sourceviewmm
> dependency was raised to 2.10 while dropping sourceview V1.
> Unfortunately this is not yet available (and won't be RSN)
> in Debian and Ubuntu. Version 2.2 is actually in the archives.
> Seemanta, you may need to build it by hand.
Right. That's in the master branch.
But in the gtk2-branch branch, the minimum version of sourceviewmm
version is still 1.9.4. So assuming Seemanta is using gtk2-branch, he
should be able to use the sourceviewmm from a reasonably recent Debian
and Ubuntu just fine.
> I tried a build lowering the dependency to 2.2 and it seems ok, but
> I'm not sure if important bugfixes got fixed in the meantime to
> support the higher requirements.
Indeed. This is why I am keeping and maintaining the gtk2-branch
around. I am actually hacking against that branch by default to make
sure things keep working for people on GNOME2. I then forward-port my
changes to master. Kalev's GNOME3 related changes go to master
directly, though.
Best.
--
Dodji
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]