--Signature=_Thu__10_Jun_2004_11_30_22_+0200_8bECjo7SZqQO.CgM
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

 > Ok, I'll create the two version.mk files for postgresql and mysql for
now. I
> thought that one file could be easier to maintain, but probably I was
> wrong.

Does this interfere and/or duplicate work wrt the proposed postgresql
pkg changes I posted to the list recently?

> Last question, should the version.mk file have a variable to specify
> the default package version? (like DB_PGSQL_DEFAULT in databases.mk)
> or just to use the installed package?

My postgresql changes have a PGSQL_VERSION_DEFAULT and
PGSQL_VERSIONS_ACCEPTED, just like pyversion.mk. I'm not that sure if
all that stuff has to be handled by database.mk. Instead it should IMHO
only include the approiate "meta-mk" for the database -- and not handle
database details. More like a global switch mysql or pgsql or ..

Cheers,
Marc

--Signature=_Thu__10_Jun_2004_11_30_22_+0200_8bECjo7SZqQO.CgM
Content-Type: application/pgp-signature

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

iD8DBQFAyCo17YQCetAaG3MRAhLoAKCBDQu+4H2llVagkxJ/GuUiLvGV5QCeIFPz
bbdsdwxr5qjRpHTiJLgOFkU=
=zxQP
-----END PGP SIGNATURE-----

--Signature=_Thu__10_Jun_2004_11_30_22_+0200_8bECjo7SZqQO.CgM--