freetype-lib and dependent packages

[Johnny C. Lam]

Hi,

The freetype library shared lib has bumped it's major library
number. How should dependent packages then check for freetype-lib?
If it's just:

DEPENDS+= freetype-lib-*:../../graphics/freetype-lib

then a binary package built with freetype-lib-1.3.1 will "match"
dependencies against freetype-lib-1.2.1, but will fail to work since
it has the wrong version of the freetype library. Should all
dependent packages now be changed to use:

DEPENDS+= freetype-lib-1.3*:../../graphics/freetype-lib

so that binary packages work correctly?

-- Johnny C. Lam <la...@stat.cmu.edu>
Department of Statistics, Carnegie Mellon University
http://www.stat.cmu.edu/~lamj/

[Hubert Feyrer]

On Mon, 24 Jul 2000, Johnny C. Lam wrote:
> DEPENDS+= freetype-lib-*:../../graphics/freetype-lib
>
> then a binary package built with freetype-lib-1.3.1 will "match"
> dependencies against freetype-lib-1.2.1, but will fail to work since
> it has the wrong version of the freetype library. Should all
> dependent packages now be changed to use:
>
> DEPENDS+= freetype-lib-1.3*:../../graphics/freetype-lib

How about:
DEPENDS+= freetype-lib>=1.3:../../graphics/freetype-lib

- Hubert

--
NetBSD - because Unix isn't just #include <linux.h>, i386, ILP32, ELF, ...!

[Johnny C. Lam]

Hubert Feyrer <fey...@rfhs8012.fh-regensburg.de> writes:
> How about:
> DEPENDS+= freetype-lib>=1.3:../../graphics/freetype-lib

The above is fine, but the point I want clarified is what to do when a
shared library's major gets bumped. Do all dependent packages need to
check for the version of the package that has the correct shared lib
version?