After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 618119 - System packages are not separated correctly in symbol-db
System packages are not separated correctly in symbol-db
Status: RESOLVED OBSOLETE
Product: anjuta
Classification: Applications
Component: plugins: symbol-db
git master
Other Linux
: Normal normal
: Anjuta 3.0
Assigned To: Massimo Cora'
Anjuta maintainers
Depends on: 623735
Blocks:
 
 
Reported: 2010-05-08 15:48 UTC by Naba Kumar
Modified: 2020-11-06 20:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Naba Kumar 2010-05-08 15:48:28 UTC
I am hard pressed to believe that gtksourceview has 688 header files to scan. So what's likely happening is that it's taking all dependencies (gtk+ et el) as part of gtksourceview.

This is during project scan (anjuta) after local .anjuta_sym_db.db has been deleted, since gtksourceview is a dependency of anjuta.

While we wait for pkg-config --list-requires, we should parse the .pc file directly, determine the deps and scan them first. We discussed in ML as well.
Comment 1 Massimo Cora' 2010-05-08 18:47:41 UTC
I think that this is more a bug project-manager related.
As discussed, the part of symbol-db-system'll be ported into pm.
Comment 2 Johannes Schmid 2010-05-09 10:50:31 UTC
It's looking fairly good that the switch will be included in pkg-config 0.24 so I wouldn't bother parsing any files by hand.
Comment 3 Naba Kumar 2010-05-09 13:30:39 UTC
(In reply to comment #2)
> It's looking fairly good that the switch will be included in pkg-config 0.24 so
> I wouldn't bother parsing any files by hand.

Good news then. Is 0.24 their next release?
Comment 4 Johannes Schmid 2010-05-09 19:36:28 UTC
> Good news then. Is 0.24 their next release?

Yes, there is a discussion about some details of the patch currently but it should go into 0.24 and that should be released in the next days.
Comment 5 Massimo Cora' 2010-05-09 20:47:08 UTC
great news!
Comment 6 Johannes Schmid 2010-05-12 08:10:28 UTC
Link to the pkg-config commit:

http://cgit.freedesktop.org/pkg-config/commit/?id=d690466af412b3735b4334842a4abc4f6e9b8a34

There will be a release within the next weeks.
Comment 7 Johannes Schmid 2010-06-29 08:48:02 UTC
We really need to use this new pkg-config support stuff for 3.0!
Comment 8 Johannes Schmid 2010-07-27 14:24:03 UTC
Just, FYI, I found out that we need to blacklist some packages like gtk+-x11-2.0 because they actually return the same include directories as gtk+-2.0 and as such we would miss those.

It's not really nice but as we only have the dependency information available it is the only way to go currently.
Comment 9 Massimo Cora' 2010-07-27 14:37:49 UTC
uhm I hope that those special cases are only a few, otherwise we will overcomplicate the system packages management, which already sucks.
Comment 10 Massimo Cora' 2010-08-16 17:31:32 UTC
as for bug #623735 moving this to milestone 3.0.
I strongly suggest that just after the release a merge with sdb-core-trans should be done, so that we have enough time to fix the problems encountered.
Comment 11 Johannes Schmid 2010-12-17 16:31:16 UTC
The code for detecting the correct headers is now in anjuta-pkg-config.[ch] in libanjuta
Comment 12 Massimo Cora' 2011-06-22 20:32:03 UTC
I'm finding some time to bring on with some bug squashing. I'd like to fix this one.
IIRC you're calling ianjuta_symbol_manager_activate_package () from language-support-cpp-java. So that I've to implement the query side and the db side to accomplish that call.
Comment 13 André Klapper 2020-11-06 20:22:26 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/anjuta/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.