--Signature=_Thu__10_Jun_2004_09_56_53_+0200_EX_7WcWtFk_wTK3o
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

On Thu, 10 Jun 2004 09:54:06 +0200
"Julio M. Merino Vidal" <jmmv@menta.net> wrote:

> Even though...  for what grant suggested, like having exim3 use different
> databases (through USE_DB="mysql postgresql"), a file in mk makes sense
> (because it's providing a "general abstraction" for database support).
> 
> If done this way, mk/databases.mk could simply need to inspect the variable
> value and then include databases/{mysql,postgresql}/version.mk depending on
> it.  And the file in mk/ could only be used by packages accepting _both_
> databases.  Packages using only one could simply include the right version.mk
> directly...

I was thinking the same when working on this file, like a generic one for all
packages requiring the same package with different versions.

I could try... :)

-- 
	Juan RP <juan@xtraeme.unixbsd.org>

--Signature=_Thu__10_Jun_2004_09_56_53_+0200_EX_7WcWtFk_wTK3o
Content-Type: application/pgp-signature

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

iD8DBQFAyBRFypkLYVDran0RAruXAJwLgrooodhhEBJ+ZIgmkQVmooHhCQCfbpO8
pBYQta4iybP4JIhmHGwMmWE=
=WDQz
-----END PGP SIGNATURE-----

--Signature=_Thu__10_Jun_2004_09_56_53_+0200_EX_7WcWtFk_wTK3o--