Date: Thu, 19 Jun 2014 16:24:04 +0200 From: Marco Steinbach <coco@executive-computing.de> To: Miroslav Lachman <000.fbsd@quip.cz> Cc: freebsd-ports@freebsd.org Subject: Re: USE_MYSQL / USE_PGSQL buildtime dependency differences Message-ID: <53A2F284.7060404@executive-computing.de> In-Reply-To: <53A2E951.2080803@quip.cz> References: <53A2DFDD.3050307@executive-computing.de> <53A2E951.2080803@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
Miroslav Lachman wrote on 19.06.2014 15:44: > Marco Steinbach wrote: >> Hi. >> >> Mk/bsd.database.mk seems to handle dependencies resulting from the use >> of USE_PGSQL and USE_MYSQL flags differently. >> >> USE_PGSQL pulls in PostgreSQL at buildtime, for both, the client and the >> server component. USE_MYSQL seems to only pull anything in at buildtime, >> if the flag is set to 'client'. >> >> Thus, with USE_MYSQL=server the build of my port breaks by not >> installing anything at buildtime, neither the server nor (more >> importantly) its client slaveport, while USE_MYSQL=client does not >> install the server. > > [...] > >> I've also tried renaming my MYSQL / PGSQL options to preclude possible >> collisions, but that didn't change behaviour. >> >> I'm trying to create a port of Icinga2 >> (https://www.icinga.org/icinga2/), FWIW. > > I think there is no need to install MySQL server on the same machine > with Icinga2 (or any other MySQL dependent port). It really needs client > library and then it can connect to any remote MySQL server. That's why > this is not supported by bsd.database.mk. Giving the user a choice for exactly this was my intention. Depend on a locally installed server, or have just the client installed. Whatever ones position on this is, the difference in behaviour of the USE_PGSQL and USE_MYSQL flags confused me. I've posted my current workaround for that on the list. MfG CoCo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53A2F284.7060404>