From owner-freebsd-ports@FreeBSD.ORG Thu Jun 18 00:01:51 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2787F106566C for ; Thu, 18 Jun 2009 00:01:51 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from QMTA04.emeryville.ca.mail.comcast.net (qmta04.emeryville.ca.mail.comcast.net [76.96.30.40]) by mx1.freebsd.org (Postfix) with ESMTP id 0D5EB8FC15 for ; Thu, 18 Jun 2009 00:01:51 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from OMTA10.emeryville.ca.mail.comcast.net ([76.96.30.28]) by QMTA04.emeryville.ca.mail.comcast.net with comcast id 5A2n1c01y0cQ2SLA4BoiG5; Wed, 17 Jun 2009 23:48:42 +0000 Received: from comcast.net ([98.203.142.76]) by OMTA10.emeryville.ca.mail.comcast.net with comcast id 5Bog1c00D1f6R9u8WBohr6; Wed, 17 Jun 2009 23:48:42 +0000 Received: by comcast.net (sSMTP sendmail emulation); Wed, 17 Jun 2009 16:48:39 -0700 Date: Wed, 17 Jun 2009 16:48:39 -0700 From: Charlie Kester To: freebsd-ports@freebsd.org Message-ID: <20090617234839.GB96132@comcast.net> Mail-Followup-To: freebsd-ports@freebsd.org References: <20090617181248.GA96132@comcast.net> <4A395100.7060509@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <4A395100.7060509@FreeBSD.org> X-Mailer: Mutt 1.5.20 X-Composer: VIM 7.2 User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: avoiding build dependency on docbook, etc. in new port X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jun 2009 00:01:51 -0000 On Wed 17 Jun 2009 at 13:24:32 PDT Greg Larkin wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >Charlie Kester wrote: >> I'm porting some software that has a build dependency on docbook2man in >> order to generate its manpages from .docbook files. >> >> Testing the port in tinderbox takes a long time, most of it because of >> the need to build the docbook infrastructure. It seems a shame to use >> all that CPU time and install all those packages just to get ready to >> convert some manpages. >> What's the preferred approach in cases like this? Should I keep the >> build dependency on docbook2man et al, or should I put pregenerated >> copies of the manpages in the files directory of the port? > >Hi Charlie, > >I feel your pain! I don't think there's any problem pre-generating the >man page and keeping it in the port's files/ directory. Actually, this is a suite of tools and there are eleven manpages. > >On the other hand, I recently went through this experience and went a >different route. YMMV! > >I took over maintainership for security/logcheck a while back, and it >used docbook2man to create its one (!) man page. After a while, I got >some requests to strip out that dependency. A user was kind enough to >point me to docbook2X: http://docbook2x.sourceforge.net/ > >This is a much lighter-weight tool for converting docbook to manual >pages, among other functions. I eventually added it to the ports tree >and updated the logcheck port to use it. Now I'm confused. When I used pkg_info to find out what package had installed docbook2man on my system, it said it was part of docbook2X-0.8.8_2. It was after I added textproc/docbook2X as a build dependency that I started seeing a bunch of docbook stuff getting installed in my tinderbox.