From owner-freebsd-python@FreeBSD.ORG Sun Jan 26 11:30:29 2014 Return-Path: Delivered-To: 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 B603ABFB for ; Sun, 26 Jan 2014 11:30:29 +0000 (UTC) Received: from smtprelay06.ispgateway.de (smtprelay06.ispgateway.de [80.67.31.96]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 74F3C1EE7 for ; Sun, 26 Jan 2014 11:30:29 +0000 (UTC) Received: from [89.182.152.226] (helo=localhost) by smtprelay06.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1W7Nuu-0007pt-Rf for python@FreeBSD.org; Sun, 26 Jan 2014 12:30:21 +0100 Date: Sun, 26 Jan 2014 12:30:22 +0100 From: Marcus von Appen To: python Subject: Re: PYDISTUTILS_AUTOPLIST question Message-ID: <20140126113022.GA1394@medusa.sysfault.org> Mail-Followup-To: python References: <52E4BCF4.3070507@yandex.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7JfCtLOvnd9MIVvH" Content-Disposition: inline In-Reply-To: <52E4BCF4.3070507@yandex.ru> User-Agent: Mutt/1.5.22 (2013-10-16) X-Df-Sender: MTEyNTc0Mg== X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Marcus von Appen List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jan 2014 11:30:29 -0000 --7JfCtLOvnd9MIVvH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On, Sun Jan 26, 2014, Ruslan Makhmatkhanov wrote: > Hi, > > while PYDISTUTILS_AUTOPLIST works smoothly for majority of ports, there > is the problem with some of them I come across yesterday. For example, > there is the port devel/py-Products.PasswordResetTool. If I set there > PYDISTUTILS_AUTOPLIST, and try to build, I got packaging error, because > some of the files, that port provides, cannot be compiled (by design). > While they are python code files, they are not supposed to be executed > with python interpreter directly (they are kind of templates). > > So, is there any possibility to: > a) Do not add compiled/optimized filenames to packing list, if the > actual file fails to compile? > b) Make a hook, that allows to list file, that should not have > corresponding *.pyc/*.pyo entries in the packing list? If the port uses distutils, it should not matter, if you do not mess around in the post-install targets yourself, since the file list will be taken from what distutils records - we do not implement magic ourselves for distutils-aware ports (well, a bit :-). If this does not work properly for you, upstream might do something that breaks the intended behaviour of distutils. So, before fixing the symptom, I actually would like to find out, what exactly they do on installation. Are all files properly recorded in ${_PYTHONPKGLIST}? What errors do you get, what does the install target complain about, etc.etc.? Cheers Marcus --7JfCtLOvnd9MIVvH Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iEYEARECAAYFAlLk8c4ACgkQi68/ErJnpkeQMACdGcI5Mqm4u1deeM4aqO1/EQYF sGUAoNaNZsD2dMjh4WOF/AwUyr9wKJar =fe8/ -----END PGP SIGNATURE----- --7JfCtLOvnd9MIVvH--