Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#34967 - Libalpm's pkgconfig reports the wrong version
Attached to Project:
Pacman
Opened by Kevin Piche (kpiche) - Friday, 26 April 2013, 01:52 GMT
Last edited by Allan McRae (Allan) - Tuesday, 30 April 2013, 11:38 GMT
Opened by Kevin Piche (kpiche) - Friday, 26 April 2013, 01:52 GMT
Last edited by Allan McRae (Allan) - Tuesday, 30 April 2013, 11:38 GMT
|
DetailsSummary and Info:
Libalpm's pkgconfig file /usr/lib/pkgconfig/libalpm.pc contains pacman's version: Version: 4.1.0 when the library version defined in configure.ac in the source is defined as: m4_define([lib_current], [8]) m4_define([lib_revision], [0]) m4_define([lib_age], [0]) Clearly the two components are tightly connected and developed together so it's understandable. For other projects libalpm does not provide an easy way to determine the library version at build time for conditional compilation. Some version #define's in alpm.h would be friendlier than having to write autoconf macros to find the library and call alpm_version(). Steps to Reproduce: cat /usr/lib/pkgconfig/libalpm.pc |
This task depends upon
Closed by Allan McRae (Allan)
Tuesday, 30 April 2013, 11:38 GMT
Reason for closing: Fixed
Additional comments about closing: git commit c1dfdd20
Tuesday, 30 April 2013, 11:38 GMT
Reason for closing: Fixed
Additional comments about closing: git commit c1dfdd20
Comment by Allan McRae (Allan) -
Friday, 26 April 2013, 02:50 GMT
I think the pkg-config file should just use the libalpm version.