How to best deal with bundled libraries

David Nalley david at gnsa.us
Mon Apr 6 02:37:17 UTC 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

A number of PHP web applications have the nasty habit of bundling
libraries with their packages.

Upstream's logic for doing so (that shared hosting might not have
access to all of the libraries in question and leave the user with no
way to install the libraries) at least seems plausible at first
glance.

However, the question I bring is how best to deal with these, at least
two options jump out at me:

1. Patch source to point to the library installed on the system rather
than the bundled
OR
2. symlink from the bundled location to the system library.

#1 strikes me as cleaner, but also more difficult to maintain.

#2 strikes me as dead easy, but also a bit more hackish.

I've talked to several people individually, and none knew of a
preference, hence I beg the wisdom of the list.



David Nalley
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAknZam0ACgkQkZOYj+cNI1cgqQCdH36WlS9haFKoi4QV0XYhwtMF
oAUAn2hGlSYMiyGtJsaJZZInCHiJV9ZT
=GrbD
-----END PGP SIGNATURE-----




More information about the fedora-devel-list mailing list