From owner-freebsd-python@FreeBSD.ORG Tue Jan 21 20:29:18 2014 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 99F07238; Tue, 21 Jan 2014 20:29:18 +0000 (UTC) Received: from forward5l.mail.yandex.net (forward5l.mail.yandex.net [84.201.143.138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5086D15B7; Tue, 21 Jan 2014 20:29:17 +0000 (UTC) Received: from smtp2h.mail.yandex.net (smtp2h.mail.yandex.net [84.201.187.145]) by forward5l.mail.yandex.net (Yandex) with ESMTP id AAA2CC40C6B; Wed, 22 Jan 2014 00:29:14 +0400 (MSK) Received: from smtp2h.mail.yandex.net (localhost [127.0.0.1]) by smtp2h.mail.yandex.net (Yandex) with ESMTP id 4A13D1700AB9; Wed, 22 Jan 2014 00:29:14 +0400 (MSK) Received: from unknown (unknown [178.76.234.16]) by smtp2h.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id HubXR9k38K-TDja7dst; Wed, 22 Jan 2014 00:29:13 +0400 (using TLSv1 with cipher CAMELLIA256-SHA (256/256 bits)) (Client certificate not present) X-Yandex-Uniq: a3e23236-072b-4b1a-88c2-06a7c218efae DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1390336153; bh=4SIG2Hyz6z0fYf034q/xY3dFkmfzMbQlCaI4LQ9ObbY=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=G6GsYIgdqUzpFu79yxQT+iohLwW5ldvqyzc6X40kzNFZGDD09f9byC8kGdY6qoEfN u2vpwoBnMUZuip3S7dNBeNHZowTWmThopEj3K39PUhwQrF3umwrUNmqw6TfymnnXzQ kowE0Q1RnOviTHSg1QnHgIujum1JJJ96W0i0aSJg= Authentication-Results: smtp2h.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <52DED896.1010308@yandex.ru> Date: Wed, 22 Jan 2014 00:29:10 +0400 From: Ruslan Makhmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-python@freebsd.org Subject: Re: Default PYTHON_PKGNAMEPREFIX and dropping PYTHON_PKGNAMESUFFIX References: <20140121104800.GA1370@medusa.sysfault.org> In-Reply-To: <20140121104800.GA1370@medusa.sysfault.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Marcus von Appen X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2014 20:29:18 -0000 Marcus von Appen wrote on 21.01.2014 14:48: > Dear all, > > most python ports, which install into PYTHON_SITELIBDIR or PYTHON_LIBDIR > use an explicit PKGNAMEPREFIX assignment to mark the resulting packages as > related to a specific python version. > The porter's handbook also outlines that ports should stick to this practice. > > I would like to force the usage of PYTHON_PKGNAMEPREFIX for ports, which use > distutils (and hence are always targeting a specific python version), by > implicitly setting PKGNAMEPREFIX=PYTHON_PKGNAMEPREFIX in bsd.python.mk. This > makes port Makefiles less error-prone and ensures that the ports stick to a > common naming scheme, when it comes to packages. > > At the same time, I would like to deprecate and remove PYTHON_PKGNAMESUFFIX, > since it has no practical use or relevance other than creating an inconsistent > package naming scheme. Its original purpose (to be read in r91400) does not > hold true in my opinion, and I am explaining the reaon(s) for that (among > other things when it comes to naming python ports) at > http://www.sysfault.org/posts/freebsd-python-ports-pre-suffix.html. > > If noone speaks up, I'll start with the necessary changes to the > infrastructure soon. > > Cheers > Marcus Like the suffix idea! I just want to add, that it would be great to also automatically adjust DOCSDIR and EXAMPLESDIR with correct prefix to make docs/examples, installed by single port, but for different python version simultaneously. This will help to avoid conflicts. Right now we have this (py-gnupg is just random python port): # make -V DOCSDIR /usr/ports/security/py-gnupg /usr/local/share/doc/gnupg So right now it ever may conflict with gnupg docs, if I understand correctly. I think that correct dirname would be: /usr/local/share/doc/py27-gnupg for python 2.7 and /usr/local/share/doc/py33-gnupg for python 3.3 The same for examples. -- Regards, Ruslan T.O.S. Of Reality