Date: Sat, 12 Jun 2010 00:16:58 +0400 From: Max Brazhnikov <makc@issp.ac.ru> To: freebsd-ports@freebsd.org Cc: Jesse Smith <jessefrgsmith@yahoo.ca> Subject: Re: Data files and ports Message-ID: <201006120016.58342.makc@issp.ac.ru> In-Reply-To: <1276284558.2503.52.camel@hp-laptop> References: <1276264730.2503.20.camel@hp-laptop> <20100611144144.GA4167@waylight.m.ringlet.net> <1276284558.2503.52.camel@hp-laptop>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 11 Jun 2010 16:29:18 -0300Fri, 11 Jun 2010 17:41:45 +0300, Jesse Smith wrote: > Thanks to everyone who replied. There were some good points made all > around. Let's say that I do decide to go with the idea of making the > Data files a separate port. How do I tell the Ports system not to try to > build the data file and instead just install the files to a location of > my choosing? Usually a project's Makefile decides what gets built and > where items go, but data packages are... dumb, they're just files. My > thought is to create a patch which adds a Makefile to the "work" > directory after the archive is untarred, which would handle the "make" > and "make install" commands. from bsd.port.mk: # NO_BUILD - Use a dummy (do-nothing) build target. # NO_INSTALL - Use a dummy (do-nothing) install target. COPYTREE_SHARE macro which copies the directory entire with its subtree and sets correct permissions can be useful for your port as well. Max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201006120016.58342.makc>