Re: Enforcing library version in a port Makefile?

2009-10-16 Thread Peter Pentchev
On Sun, Oct 11, 2009 at 09:49:28AM -0500, Alex Stangl wrote: On Sun, Oct 11, 2009 at 05:15:58AM +, b. f. wrote: Alex Stangl wrote: I am trying to create a new port. The software I am trying to port uses scons which calls out to pkg-config to check for certain minimal library version

Re: Enforcing library version in a port Makefile?

2009-10-15 Thread b. f.
On 10/11/09, Alex Stangl a...@stangl.us wrote: On Sun, Oct 11, 2009 at 05:15:58AM +, b. f. wrote: Alex Stangl wrote: ... 2. If user upgrades ports and gets lib.M+1, make fails because the exact match is no longer satisfied. (Porter's Handbook says you can use LIB_DEPENDS regular

Re: Enforcing library version in a port Makefile?

2009-10-11 Thread Alex Stangl
On Sun, Oct 11, 2009 at 05:15:58AM +, b. f. wrote: Alex Stangl wrote: I am trying to create a new port. The software I am trying to port uses scons which calls out to pkg-config to check for certain minimal library version #s (e.g., sndfile = 1.0.18, libcurl = 7). I would like to

Enforcing library version in a port Makefile?

2009-10-10 Thread Alex Stangl
Hi, I am trying to create a new port. The software I am trying to port uses scons which calls out to pkg-config to check for certain minimal library version #s (e.g., sndfile = 1.0.18, libcurl = 7). I would like to enforce these same checks upfront in the Makefile rather than letting the build

Re: Enforcing library version in a port Makefile?

2009-10-10 Thread b. f.
Alex Stangl wrote: I am trying to create a new port. The software I am trying to port uses scons which calls out to pkg-config to check for certain minimal library version #s (e.g., sndfile = 1.0.18, libcurl = 7). I would like to enforce these same checks upfront in the Makefile rather than