I think this is the bug I want to report - so to clarify the issue:
To start a new project in Anjuta, you go through a new project wizard,
select one of the GUI project-types (Gnome2.0, GTK 2.0, LibGlade 2.0 or
gtkmm 2.0), fill in the various fields and click the apply button.
Anjuta opens and
Clearly Anjuta does depend on libglib2.0-dev because I've just installed
it and the Anjuta new project wizard now works.
--
Anjuta and glib [breezy]
https://launchpad.net/bugs/24981
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Now I don't remeber what was the problem with libglib2.0-dev, but if you
install anjuta on kubuntu dapper project autogeneration (starting a new
project) fails unless you have installed autoconf, automake and libtool
by hand.
kdevelop3 depends on autoconf and automake.
--
Anjuta and glib
I've subscribed the MOTU to this bug. Hopefully they know more about
what should be done than I do. I'm just a lowly bug triager!
--
Anjuta and glib [breezy]
https://launchpad.net/bugs/24981
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Hello!
I'm afraid you are on your own with this bug since I don't have time to
follow development branch any more.
Thanks anyway!
--
Anjuta and glib [breezy]
https://launchpad.net/bugs/24981
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
When you said you couldn't autogenerate the project, what exactly where
you talking of?
This bug was reported in breezy, but current stable is dapper. Is that
what you meant by development branch? Current testing release is Edgy
Eft.
If you don't have time to work on the bug I'll close it
http://packages.ubuntu.com/dapper/gnome/anjuta
It appears that anjuta still does not depend directly on libglib2.0-dev or
build-essential.
Is there still a need for anjuta to depend on either of these packages?
Thanks for the bug report.
** Changed in: Ubuntu
Sourcepackagename: None = anjuta
