'Package foo was not found' when version doesn't match #3

New Issue

ariadne · 2012-05-03T06:58:36Z

mgorny commented

2012-05-03 06:58:36 +00:00

(Migrated from github.com)

$ PKG_CONFIG_PATH=tests/lib1 ./pkgconf --exists 'foo > 1.2.3'; echo $?
Package foo was not found in the pkg-config search path.
Perhaps you should add the directory containing `foo.pc'
to the PKG_CONFIG_PATH environment variable
No package 'foo' found
1

The message is unclear here. foo.pc actually exists but it is too old. To compare:

$ PKG_CONFIG_PATH=tests/lib1 pkg-config --exists 'foo > 1.2.3'; echo $?
1
+ [OK]

``` $ PKG_CONFIG_PATH=tests/lib1 ./pkgconf --exists 'foo > 1.2.3'; echo $? Package foo was not found in the pkg-config search path. Perhaps you should add the directory containing `foo.pc' to the PKG_CONFIG_PATH environment variable No package 'foo' found 1 ``` The message is unclear here. `foo.pc` actually exists but it is too old. To compare: ``` $ PKG_CONFIG_PATH=tests/lib1 pkg-config --exists 'foo > 1.2.3'; echo $? 1 + [OK] ```

ariadne commented

2012-05-03 17:35:39 +00:00

indeed, this is because pkg_verify_dependency() only returns yes/no. we should extend it to return more than that.

Sign in to join this conversation.