From owner-freebsd-ports@FreeBSD.ORG Mon Jul 23 23:51:38 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B11C0106566C for ; Mon, 23 Jul 2012 23:51:38 +0000 (UTC) (envelope-from ian@ndwns.net) Received: from smtpauth.rollernet.us (smtpauth.rollernet.us [IPv6:2607:fe70:0:3::d]) by mx1.freebsd.org (Postfix) with ESMTP id 917028FC0A for ; Mon, 23 Jul 2012 23:51:38 +0000 (UTC) Received: from smtpauth.rollernet.us (localhost [127.0.0.1]) by smtpauth.rollernet.us (Postfix) with ESMTP id 77414594012 for ; Mon, 23 Jul 2012 16:51:36 -0700 (PDT) Received: from localhost (c-76-126-116-195.hsd1.ca.comcast.net [76.126.116.195]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtpauth.rollernet.us (Postfix) with ESMTPSA for ; Mon, 23 Jul 2012 16:51:35 -0700 (PDT) Date: Mon, 23 Jul 2012 16:51:35 -0700 From: Ian Downes To: freebsd-ports@freebsd.org Message-ID: <20120723235135.GA39648@weta.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-Rollernet-Abuse: Processed by Roller Network Mail Services. Contact abuse@rollernet.us to report violations. Abuse policy: http://www.rollernet.us/policy X-Rollernet-Submit: Submit ID 30d9.500de387.f1b14.0 Subject: port pkg-plist when files change every build? 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: Mon, 23 Jul 2012 23:51:38 -0000 I'm porting an application (RStudio server) which generates files with unique names every time you build it. The files are web resources (javascript, images etc) and I don't have any control over their naming. What's the recommended way to deal with this? My current thought is to install to a staging dir in WRKSRC and then dynamically build the plist from there during pre-install before cp'ing to the actual install dir. I don't think it's a problem that a package has a particular set of names. thanks, Ian