PKGCONF_PKG_PKGF_SIMPLIFY_ERRORS is not always considered #134

Closed
opened 2017-09-12 23:02:20 +00:00 by karen-arutyunov · 0 comments
karen-arutyunov commented 2017-09-12 23:02:20 +00:00 (Migrated from github.com)

Currently the PKGCONF_PKG_PKGF_SIMPLIFY_ERRORS flag is considered only in a single place of pkgconf_pkg_report_graph_error() function, so just the main error message is reported to the client-supplied error handler.

Shouldn't this flag be considered in other places as well, specifically in the rest of pkgconf_pkg_report_graph_error() and in pkgconf_pkg_walk_conflicts_list() ?

The rationale for this is that the additional error messages usually contain some hints that mention pkg-config-specific environment variables that can be irrelevant for an executable that links libpkgconf library, and being printed confuse its users.

Currently the PKGCONF_PKG_PKGF_SIMPLIFY_ERRORS flag is considered only in a single place of pkgconf_pkg_report_graph_error() function, so just the main error message is reported to the client-supplied error handler. Shouldn't this flag be considered in other places as well, specifically in the rest of pkgconf_pkg_report_graph_error() and in pkgconf_pkg_walk_conflicts_list() ? The rationale for this is that the additional error messages usually contain some hints that mention pkg-config-specific environment variables that can be irrelevant for an executable that links libpkgconf library, and being printed confuse its users.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: ariadne/pkgconf#134
There is no content yet.