Date: Wed, 14 May 2014 09:54:36 +0200 From: John Marino <freebsd.contact@marino.st> To: freebsd-ports@freebsd.org Subject: Re: r353029 broke net-mgmt/zabbix2*-server options Message-ID: <5373213C.7040102@marino.st> In-Reply-To: <CAAoTqfuADqMFrE%2B8mmWJTAhF9SX=E89iLmQ3KNSaqSN40Anfnw@mail.gmail.com> References: <CAAoTqfuADqMFrE%2B8mmWJTAhF9SX=E89iLmQ3KNSaqSN40Anfnw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/14/2014 09:42, Pavel Timofeev wrote: > Hi! > After this commit to regular ports tree both zabbix (2.0 and 2.2) > ports was messed. > For example: > ====> Options available for the single DB: you have to select exactly > one of them > MYSQL=on: MySQL database support > PGSQL=off: PostgreSQL database support > SQLITE=off: SQLite database support > ORACLE=off: Oracle database support > ODBC=off: Support for database checks via ODBC > ===> Use 'make config' to modify these settings > > ODBC shouldn't be in DB section. See in 2014Q2 - that's how it has to > look. Please, fix it I am somebody completely unfamiliar with this port. So I am curious why "ODBC shouldn't be in DB section". ODBC is a database driver, so why shouldn't it be in the database section? You state it needs to be a certain way, but the justification is that it was that way before rather than stating the real reason for those of us that aren't familiar with this particular port. Thanks, John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5373213C.7040102>