Arch Linux

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#11594 - inconsistent lib naming

Attached to Project: Arch Linux
Opened by Christ Schlacta (aarcane) - Saturday, 27 September 2008, 00:11 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 05 October 2008, 10:52 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

lib packages have somewhat inconsistent names. for example:
libmysqlclient
postgresql-libs

I've noticed other examples of this in the past, and I think libs should be renamed more consistently so that when looking for a lib, you can just type in libwhatever instead of having to guess which name format the library uses or search for it in the package db.
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Sunday, 05 October 2008, 10:52 GMT
Reason for closing:  Won't implement
Comment by Roman Kyrylych (Romashka) - Sunday, 05 October 2008, 10:52 GMT
http://www.archlinux.org/packages/search/?q=-libs
1) *-libs is the minority, and all of them are named this way either because upstream does this or because there are more than one lib in a package (and it was splitted from another package)
2) libmysqlclient contains only one lib, postgresql-libs contains more, and neither of them is called libpostgresql

Loading...