Arch Linux

Please read this before reporting a bug:

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!

FS#43013 - [libgit2] requesting static lib package

Attached to Project: Arch Linux
Opened by Shawn Rutledge (ecloud) - Friday, 05 December 2014, 06:32 GMT
Last edited by Jan de Groot (JGC) - Thursday, 11 December 2014, 10:49 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


Upstream keeps making API changes which tend to break other packages. In particular I keep trying to use (for which there is no Arch package yet). Often it doesn't build. When I get lucky and it does build, it would be nice to have it statically linked so that it doesn't break again later.

I wonder how the pygit2 egg manages to stay in sync.
This task depends upon

Closed by  Jan de Groot (JGC)
Thursday, 11 December 2014, 10:49 GMT
Reason for closing:  Won't implement
Comment by Jan de Groot (JGC) - Friday, 05 December 2014, 09:28 GMT
I don't see this as a valid reason for a distribution package. If your software can't keep up with development you should include a specific version in-tree so your software always compiles. This is what Mozilla does with firefox and cairo for example. Even if we include the static library, the next bugreport that gets opened is "can't compile".