From owner-svn-ports-all@FreeBSD.ORG Mon Mar 11 14:03:12 2013 Return-Path: Delivered-To: svn-ports-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 76CFCF54; Mon, 11 Mar 2013 14:03:12 +0000 (UTC) (envelope-from makc@freebsd.org) Received: from mail.issp.ac.ru (mail.issp.ac.ru [77.236.34.3]) by mx1.freebsd.org (Postfix) with ESMTP id D60DA3D2; Mon, 11 Mar 2013 14:03:11 +0000 (UTC) Received: from mercury.ph.man.ac.uk [130.88.75.175:60795] (HELO/EHLO mercury.ph.man.ac.uk, authenticated with LOGIN) by mail.issp.ac.ru with ESMTP/inet id r2BE39LX006926 (using TLSv1/SSLv3, with cipher DHE-RSA-AES256-SHA (256 bits), verified NO) Mon, 11 Mar 2013 18:03:10 +0400 (MSK) From: Max Brazhnikov To: Alexey Dokuchaev Subject: Re: svn commit: r313841 - head/comms/openobex Date: Mon, 11 Mar 2013 14:04:12 +0000 Message-ID: <1814448.jXEQ24LmKk@mercury.ph.man.ac.uk> User-Agent: KMail/4.9.5 (FreeBSD/9.1-STABLE; KDE/4.10.1; amd64; ; ) In-Reply-To: <20130311013156.GA73813@FreeBSD.org> References: <201303102105.r2AL5C2o048218@svn.freebsd.org> <20130311013156.GA73813@FreeBSD.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="koi8-r" Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, Guido Falsi , ports-committers@freebsd.org X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 14:03:12 -0000 On Mon, 11 Mar 2013 01:31:56 +0000 Alexey Dokuchaev wrote: > On Sun, Mar 10, 2013 at 09:05:12PM +0000, Guido Falsi wrote: > > New Revision: 313841 > > URL: http://svnweb.freebsd.org/changeset/ports/313841 > > > > Log: > > - Fix plist when DOXYGEN option is enabled but DOCS is not > > - Enable DOXYGEN option by default > > Would it be feasible to make DOXYGEN default for bulk pacakge building > cases but not for regular port users (that is, hide it behind BATCH or > PACKAGE_BUILDING)? Sounds good. But not only doxygen is used to generate documentation, e.g. the doxygen port uses latex and graphviz to generate its own docs. We may consider introduce BUILD_DOCS option along with DOCS. The later should be used only for for installing files shipped with the source tarball, while the former would imply additional dependencies for generating documentation. Of cause it wouldn't be a problem to have BUILD_DOCS enabled for PACKAGE_BUILDING, until it's explicitly requested by user. Max