cvs commit: ports/games/py-pychess Makefile

[Chris Rees]

2011/12/13 Alexey Dokuchaev <danfe at freebsd.org>:
> On Mon, Dec 12, 2011 at 06:21:12PM +0400, Ruslan Mahmatkhanov wrote:
>> Nicola Vitale wrote on 12.12.2011 17:51:
>> >> [2011/12/12 Alexey Dokuchaev <danfe at freebsd.org>]
>> >> [...] perhaps you could consider moving this to a better
>> >> named "games/pychess".  Note that py- prefix should not be used for
>> >> normal applications.
>> >
>> > AFAIK, py- prefix should be used for all port that install files under
>> > PYTHON_SITELIBDIR, i.e., that use PYTHON_PKGNAMEPREFIX in their
>> > package name.
>
> I've always wondered how this discussion spawns again and again.  :-)
>
> To put it shortly, what's more important is that such ports install files
> under "bin/" -- which is the first thing our users care about, not whether
> it uses any resources or libraries for its operation (those that go under
> PYTHON_SITELIBDIR).
>
> Actually, we have two issues here (quoting my earlier email to cs@):
>
> 1) what should be name of the port directory?  My answer is "pychess".  As a
> user, I don't really care which language was used to write software.  I want
> a chess client, and google tells me there is one named "pychess".  So I
> will naturally try to look for it spelled like that.
>
> 2) what should be PKGNAME?  Less obvious, but then I'll ask myself, why do I
> need to embed the Python version in the package name?  Given sufficient
> reasons I might agree, but so far as I see it, it is a self-contained port
> with bunch of its local Python stuff under PYTHON_SITELIBDIR, and tainting
> both port directory and package name does not bring any noticeable good.
>
>> > audio/py-sonata or www/google-appengine -> www/py-google-appengine,
>> > even if they were Python applications.
>> > Otherwise, we should rename hundreds of ports, not only that one.
>
> Ideally, yes, however, the cost of such rename is a bit too high.  Instead
> we should refine our documentation in this area and try to be more careful
> in the future.
>
>> Hmm, i though that PYTHON_PKGNAMEPREFIX is added only if the port in
>> question - it's a library. For that reason i omitted py-prefix for
>> deskutils/gtg, multimedia/gtk-recordmydesktop, www/zope213 etc. All of
>> them install their files into %%PYTHON_SITELIBDIR%%.
>
> Yes, exactly.  Prefixes are for libraries, extensions, bindings, plugins,
> etc. -- "batteries", not for "normal" applications and utilities.

Cool.

Perhaps this could be discussed on ports@ and then documented?

Chris