split pkgconf-specific behaviours out into a separate test battery, document differences better #90

New Issue

ariadne · 2016-05-28T08:56:08Z

ariadne commented

2016-05-28 08:56:08 +00:00

right now, our test suite tests both conformance of pkg-config implementations, as well as pkgconf-specific features and quirks.

we should both split out the pkgconf-specific extensions (so any pkg-config implementation can be tested against our testsuite and pass it), as well as document the reasons behind those extensions/differences (mostly relating to how sysroot is handled)

right now, our test suite tests both conformance of pkg-config implementations, as well as pkgconf-specific features and quirks. we should both split out the pkgconf-specific extensions (so any pkg-config implementation can be tested against our testsuite and pass it), as well as document the reasons behind those extensions/differences (mostly relating to how sysroot is handled)

ariadne commented

2016-11-05 15:51:11 +00:00

Poster

This was done as part of #96 I suppose.

Sign in to join this conversation.