GNOME Bugzilla – Bug 625657
add system packages filtering
Last modified: 2020-11-06 20:23:06 UTC
@Naba: I don't see in symbol-db-query a mechanism to query only the system packages selected from the user, through preferences. I.e. 'system packages' = 'projects' in the db. Global db is structured like this: a package on system, say for instance gtk+-2.0, is a project entry, with its associated files and symbols. Currently I see that there's no distinction on them and that every query is performed on the whole system db. Due to bug #623735 we need that filters. I'm already done with the interface part and I'm quite ready to remove symbol-db-system stuff. We only need a way to implement this. Being the person who wrote symbol-db-query I suppose the best choice is that you implement that, or if you haven't time, you can explain me how you would implement that. Btw: I've added a 'project_version' field on project table, so that the language-support plugins can manage multiple versions of packages without being forced to rely on pkg-config stuff. I'm pushing the changes on sdb-core-trans branch.
as from bug #623735 I put this to milestone 3.0
FYI, there are some helper functions to deal with pkg-config in anjuta-pkg-config.h. These should help to correctly identify individual files of packages. Please put all pkg-config specific code in that file so we have a centralized place to deal with things. I am not sure if it is useful to add a project version. ABI breakage is usually indicated by a new pkg-config name (gtk+-2.0 vs. gtk+-3.0). But we could use the pkg-config supplied version as timestamp and rescan when the version is increased.
(In reply to comment #2) > FYI, there are some helper functions to deal with pkg-config in > anjuta-pkg-config.h. These should help to correctly identify individual files > of packages. Please put all pkg-config specific code in that file so we have a > centralized place to deal with things. > sure. Do you plan to remove the package-selector on language-support-cpp-java preferences? We may automatically load the required packages without forcing user to select them. > I am not sure if it is useful to add a project version. ABI breakage is usually > indicated by a new pkg-config name (gtk+-2.0 vs. gtk+-3.0). But we could use > the pkg-config supplied version as timestamp and rescan when the version is > increased. well, we may have gtk+-2.0 as package name but version 2.20.1 as in $ pkg-config --modversion gtk+-2.0 2.20.1 I suppose that ProjectManager gives the apis to access the packages' headers as List<gchar*> get_packages(); List<GFile *> get_elements (AnjutaProjectNodeType element_type);
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.