From owner-freebsd-ports@FreeBSD.ORG  Wed Jul 20 20:40:46 2011
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
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 E3C9C106566B
	for <freebsd-ports@FreeBSD.org>; Wed, 20 Jul 2011 20:40:46 +0000 (UTC)
	(envelope-from stephen@missouri.edu)
Received: from wilberforce.math.missouri.edu (wilberforce.math.missouri.edu
	[128.206.184.213])
	by mx1.freebsd.org (Postfix) with ESMTP id B10C78FC08
	for <freebsd-ports@FreeBSD.org>; Wed, 20 Jul 2011 20:40:46 +0000 (UTC)
Received: from [127.0.0.1] (wilberforce.math.missouri.edu [128.206.184.213])
	by wilberforce.math.missouri.edu (8.14.4/8.14.4) with ESMTP id
	p6KKeiUK024387
	for <freebsd-ports@FreeBSD.org>; Wed, 20 Jul 2011 15:40:45 -0500 (CDT)
	(envelope-from stephen@missouri.edu)
Message-ID: <4E273D4C.6060105@missouri.edu>
Date: Wed, 20 Jul 2011 15:40:44 -0500
From: Stephen Montgomery-Smith <stephen@missouri.edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.9.2.18) Gecko/20110617 Thunderbird/3.1.11
MIME-Version: 1.0
To: FreeBSD Ports <freebsd-ports@FreeBSD.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 
Subject: portlint: DATADIR and NOEXAMPLEDOCS
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2011 20:40:47 -0000

I have a couple of questions.

1)  Why does portlint complain if a port is not DATADIR compliant?

What was the rationale behind making ports DATADIR compliant, so that if 
one types "make install DATADIR=/somewhere_else" then what would be 
stored in /usr/local/share/port_name will now be in /somewhere_else.

If there are one hundred ports depending upon port x/y, and those ports 
use the x/y DATADIR, then each of those hundred ports will have to include:
DATADIR!=	cd ${.CURDIR}/../../x/y && make -V DATADIR

This will really slow down makeindex.

It seems to me that you cannot use:
DATADIR=	`cd ${.CURDIR}/../../x/y && make -V DATADIR`
because this won't properly set PLIST_SUB.

2)  Why does portlint NOT complain if a port is not NOPORTEXAMPLES 
compliant?

This would seem a natural extension of portlint complaining if a port is 
not NOPORTDOCS compliant.

Stephen