Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

This adds support for building foreign libraries with a given ABI version on Linux. This is enables foreign libraries to specify ABI compatibility information. This is important since ABI compatibility differs from package release versions.

Two new fields are added: lib-version-info and lib-version-linux. The former accept versions Libtool-style, the latter sets SONAME versions directly. In both cases, appropriate symlinks are installed.

Libtool accepts ABI version data via the -version-info flag, which takes current[:revision[:age]] data. This is then parsed into a major.minor.build version number. We copy this approach so that library versioning may be generalised to other operating systems than Linux.

See cabal-testsuite/README.md for a detailed description
of the new architecture.

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Edward Z. Yang authored 8 years ago and Edward Z. Yang committed 8 years ago

Previously, the code would unconditionally report that internal
dependencies were satisfiable, even if --exact-configuration was
provided, we're in per-component mode, and the internal lib was
NOT supplied via a --dependency parameter.  Now ./Setup configure
correctly fails at the right stage.

There is a bit of wibbling to do with compatibility package names.
I think I've gotten it right.

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Also gets rid of `Distribution.Packages.TextClass`

Edward Z. Yang authored 8 years ago and Edward Z. Yang committed 8 years ago

Now that cabal-testsuite uses a Custom setup, we can assume
that we are able to read the LBI from our build.  This is good
news, because the old algorithm didn't really work at all
(and stopped working with cabal-install-1.24.0.1)

Fixes #4108.

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Since this fixes #3858

Duplication introduced by #4065.

Auke Booij authored 8 years ago and Edward Z. Yang committed 8 years ago

Also bump version requirements for foreign libs (ghc>=7.8)

Edward Z. Yang authored 8 years ago and Edward Z. Yang committed 8 years ago

The key idea is that once we put PackageTests in its own package, we can
ensure that its Setup.hs is compiled with the same version of Cabal
library as package-tests is compiled with.  This means that LBI reading
will *always succeed* which is quite nice.

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>