--==========972970681F01C5FB2BC2==========
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

> I guess if a package does require a specific version will also need to
> take steps to make sure that it only runs against the version it was
> built for.  Do you have an example of such a package or is this just
> thinking ahead?

More the latter. I'm currently in the process of converting the packages to =

mk/pgsql.buildlink3.mk and hope that I don't come across any major=20
problem... ;-)
While doing this I started to doubt pgsql.buildlink3.mk is the correct=20
name, though. Since it also works without buildlink3. Maybe I should rename =

it to pgsql.lib.mk?

Cheers,
Marc

--==========972970681F01C5FB2BC2==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFBAkAh7YQCetAaG3MRAsDTAJ9km0QKHFiLcLSIDGUvjvuW0q5QsgCffV4f
GM/lZqmoCh+zz3M6vIVjHlY=
=yse4
-----END PGP SIGNATURE-----

--==========972970681F01C5FB2BC2==========--