[anjuta-devel] Glade catalog configure switch

[James Liggett <jrliggett cox net>]

Hi all,
For a while now our glade catalog has been installed into Anjuta's
install prefix. This change was made so that users wouldn't be required
to have root privileges if they were installing to a prefix that they
can write to. If glade happens to be installed in that prefix, the glade
catalog works as well, but if your glade install is in a different
prefix, like mine is, the glade catalog isn't usable unless you copy the
catalog files into the appropriate places manually.

To properly fix this, I've added a new switch to configure,
--enable-glade-catalog, which will build the glade catalog only for
developers who need it. This option is off by default, so users who
don't use it won't have to worry about it. You should only need to use
this switch if you work on a plugin that needs it, like git, subversion,
or the project manager. But, if you enable this option, you may need
root privileges to install Anjuta if you don't have write access to the
place where glade is installed.

I think this solution is a reasonable compromise. 99% of our users don't
use the glade catalog so this problem won't exist for them at all. And
for the handful of us that do use the catalog, we just have to remember
to pass --enable-glade-catalog to configure and the build system will do
the rest, just like it used to.

If you use the glade catalog for your plugin, please test this new
option and report any problems.

Thanks,
James