Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#40406 - Strange library names

Attached to Project: Community Packages
Opened by Andreas Baumann (andreas_baumann) - Saturday, 17 May 2014, 10:04 GMT
Last edited by Allan McRae (Allan) - Saturday, 17 May 2014, 11:35 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

/usr/lib/libhpdf-2.2.1.so

libhpdf.so -> libhpdf-2.2.1.so

IMHO this should as follows:

/usr/lib/libhpdf.so.2.2.1
/usr/lib/libhpdf.so.2 -> /usr/lib/libhpdf.so.2.2.1
/usr/lib/libhpdf.so -> /usr/lib/libhpdf.so.2.2.1

libharu is version 2.2.1-5.

I also like to link binaries statically sometimes, so

/usr/lib/libhpdf.a

would also be nice.

I don't get the point of not having static libraries around
in a distribution? Also a separation into runtime and development
packages would be an idea. The development packages containing the
/usr/lib/libhpdf.so, /usr/lib/libhpdf.a and the header files.

This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 17 May 2014, 11:35 GMT
Reason for closing:  Not a bug
Comment by Karol Błażewicz (karol) - Saturday, 17 May 2014, 11:21 GMT
Have you read https://mailman.archlinux.org/pipermail/arch-dev-public/2013-September/025454.html ?
Comment by Allan McRae (Allan) - Saturday, 17 May 2014, 11:35 GMT
Talk to upstream about their (lack of) library versioning. What is provided in the package is direct from upstream.

Also, we are not splitting developmental files or providing static libraries.

Loading...