From owner-svn-ports-all@FreeBSD.ORG Thu May 16 01:20:23 2013 Return-Path: Delivered-To: svn-ports-all@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1033) id 38FE2C20; Thu, 16 May 2013 01:20:23 +0000 (UTC) Date: Thu, 16 May 2013 01:20:23 +0000 From: Alexey Dokuchaev To: Johan van Selst Subject: Re: svn commit: r318127 - in head/games/xboard: . files Message-ID: <20130516012023.GA68576@FreeBSD.org> References: <201305132020.r4DKKTen074755@svn.freebsd.org> <20130514201011.GA50950@mud.stack.nl> <1722947.Vxd1CHFxaz@mercury.ph.man.ac.uk> <20130515165856.GA93563@mud.stack.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130515165856.GA93563@mud.stack.nl> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "svn-ports-head@freebsd.org" , Max Brazhnikov , "svn-ports-all@freebsd.org" , Jason Helfman , "ports-committers@freebsd.org" X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2013 01:20:23 -0000 On Wed, May 15, 2013 at 06:58:56PM +0200, Johan van Selst wrote: > Max Brazhnikov wrote: > > Another alternative is to not use PORTDATA. Besides does xboard work > > without PORTDATA files? > > Yes, the port works fine without PORTDATA files, although it will print > a warning because you will be playing chess with invisible pieces > unless you add a custom tileset ;-) > > Maybe I should just remove the PORTDATA option to prevent people from > actually doing such silly things. +1. I actually find entire concept of PORTDATA quite bogus. Apparently it supposed to be akin to PORTDOCS, but I don't think it can work this way: while docs usually is just a pile of files mainly of users' interest, not required by application at run time, PORTDATA (resources) are essential part of it. I can hardly expect why would anyone want to separate resources from the port. Heavy games are special, but again, we just create separate -data port with heavy stuff, and game port with non-heavy resources and binaries, without the silly PORTDATA. While PORTDOCS can cause similar annoyance sometimes, PORTDATA imho is just broken by design. ./danfe