Hi! (commenting here instead of the bug)
I think you do it on purpose. Then we have get several bug reports, especially to remove deprecated features that require to use of the latest development version. So, that's fine for me to decide that Anjuta needs the latest version of several libraries.
I tried to wait quite long for it but as Naba accepted the patch and set it to "commit-now" I rather wanted to get it in before the last beta release. The problem to me is also that the feature is currently not working for me and I didn't want to investigate with the old code.
But, then I think it would be nice to add more informations on how to compile Anjuta from sources. It will be useful for developers outside the core team and even for us. How do you handle this on your side ? Do you use a development version of your distribution ? Do you use jhbuild ?
Normally I try to keep everything working on the last stable version of the distribution. Usually the only thing I compile from source if gdl, libgda and glade3. I remember that you said that updating glib wasn't a big deal in the past so I tried it here and after adjusting the libdir (/usr/lib64) everything worked fine. So, now I am using a new unstable glib, too. But you are right that we should have much better information on how to build anjuta. I will try to update the development site on the webpage before the release but I cannot promise it.
I have been able to compile Anjuta on a very old system (Red Hat 4.5 or 4.6) using jhbuild. It takes some time because I have to recompile almost the whole GNOME stack. I wasn't able to recompile gdm though due to changes in the power management. I got some issues with file notification too, this kernel was using dnotify and I think Anjuta uses too many monitors for it, so the performance is really bad. GEdit was working much better because it checks changes on the currently open file only.
Hmm, maybe we should do that too and only check for changes one the current document changes. Can you file a bug about it?
On my previous system, I have been able to compile Anjuta after compiling Glib, Gtk and several other libraries from sources in /usr/local. But I have to tune some .pc and .la files in /usr/local/lib and /usr/local/pkgconfig due to libraries used by Anjuta and depending on Glib and Gtk (all components should use the same version of Glib in /usr/local/lib). It's possible but not easy. Do you have a better solution ? In both case, on things that help is to minimize dependencies and avoid mandatory plugins. devhelp by example needs webkit that needs a lots of libraries.
We could make devhelp optinally (I think that's trivial). As I said above I usually don't use jhbuild because even on a quad-core it just takes hours and often fails in strange places. That is one of the reasons that we try to never depend on an unstable gtk+ version. If you are all unkomfortable with building the new glib version than please revert that patch. Note though that the glib also finally has a GType for GError which removes some files from libanjuta and makes things cleaner. Thanks and regards, Johannes
Attachment:
signature.asc
Description: This is a digitally signed message part