From owner-freebsd-ports@FreeBSD.ORG  Thu Mar 29 07:54:56 2012
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@freebsd.org
Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35])
	by hub.freebsd.org (Postfix) with ESMTP id EAE8B1065673
	for <ports@freebsd.org>; Thu, 29 Mar 2012 07:54:56 +0000 (UTC)
	(envelope-from dougb@FreeBSD.org)
Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36])
	by mx2.freebsd.org (Postfix) with ESMTP id 79E94164499;
	Thu, 29 Mar 2012 07:54:23 +0000 (UTC)
Message-ID: <4F74152F.4090302@FreeBSD.org>
Date: Thu, 29 Mar 2012 00:54:23 -0700
From: Doug Barton <dougb@FreeBSD.org>
Organization: http://www.FreeBSD.org/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Chris Rees <utisoft@gmail.com>
References: <CADLo839cUtxHJNqYQtvaFSp9Jjg21Hsn0U7xiOS9JuGmkhETmg@mail.gmail.com>
In-Reply-To: <CADLo839cUtxHJNqYQtvaFSp9Jjg21Hsn0U7xiOS9JuGmkhETmg@mail.gmail.com>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ports@freebsd.org
Subject: Re: How useful is %%DATADIR%%, anyway?
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: Thu, 29 Mar 2012 07:54:57 -0000

On 3/23/2012 1:14 PM, Chris Rees wrote:
> Just as a thought, I decided to try stripping out all mentions of
> %%DATADIR%%, %%DOCSDIR%% etc from pkg-plist, and replacing them with
> PORTDOCS=*, PORTDATA=* in the Makefiles etc.

How much time does creating the dynamic plists take for ports with
larger numbers of docs/data, vs. the static lists; and how many ports
would be adversely affected, if any?

In regards to the idea itself, I like dynamic (or more dynamic) plist
generation whenever possible, so I think you're going the right direction.

One small note, some of us use a construction like this:

PORTDOCS=	foo bar baz

post-install:
.for file in ${PORTDOCS}
	...
.endfor

So taking into consideration that '*' might not always be literally '*',
I'm in favor.

hth,

Doug