Date: Thu, 13 Dec 2018 10:35:04 +0100 From: Mathieu Arnold <mat@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org> Cc: Michael Gmelin <grembo@freebsd.org>, FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Best way to deal with .pyc files? Message-ID: <20181213093504.vwene4mp5cy5ehgd@atuin.in.mat.cc> In-Reply-To: <d24044c0-b620-f7fa-63e6-bc446134c988@FreeBSD.org> References: <f2c1b368-cd2e-85a3-a5c7-794d69204625@FreeBSD.org> <8D6D9096-468D-4E69-A6F2-79142C52395C@freebsd.org> <b37ea393-6321-826d-7c31-153a0822de87@FreeBSD.org> <d24044c0-b620-f7fa-63e6-bc446134c988@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--774jyfxxesn4kttv
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Dec 10, 2018 at 11:22:49AM -0800, John Baldwin wrote:
> On 12/7/18 10:17 AM, John Baldwin wrote:
> > On 12/6/18 11:17 AM, Michael Gmelin wrote:
> >>
> >>
> >>> On 6. Dec 2018, at 19:21, John Baldwin <jhb@freebsd.org> wrote:
> >>>
> >>> The devel/gdb port installs python scripts into /usr/local/share/gdb<=
ver>/python.
> >>> If you then run kgdb as root (not that unusual), it will generate .py=
c files in
> >>> those directories that are not deleted by 'pkg delete'. What is the =
best way to
> >>> handle this case? Should the pkg-plist include @rmtry entries for ea=
ch pyc
> >>> file or is there a better way?
> >>>
> >>
> >> Pre-generate the pyc files on package build and install them with the =
port, so they become part of plist (there are examples of that in the ports=
tree, whenever possible for both py27 and py3x).
> >=20
> > Ok. One follow-up question. GDB's python bindings work with both py2 =
and
> > py3, but the bindings are optional. Right now PYTHON is a port option
> > (but on by default). If I wanted to add flavors I would probably want =
them
> > to be conditional on the option, so the results would be 'gdb' and
> > 'gdb-py3' packages by default, but if someone was using poudriere local=
ly
> > and disabled python, I would only want to build a single 'gdb' without
> > python. So, can I make the flavors conditional on an option or is it t=
oo
> > late to define flavors after including bsd.ports.options.mk?
> >=20
> > That is, can I do something this:
> >=20
> > OPTIONS_DEFINE=3D PYTHON
> > OPTIONS_DEFAULT=3D PYTHON
> >=20
> > .include <bsd.port.pre.mk>
> >=20
> > .if ${PORT_OPTIONS:MPYTHON}
> > USES_PYTHON=3D flavors
> > .endif
>=20
> FYI, this worked:
All things considered, it does not matter when you set
USE_PYTHON=3Dflavors because it does nothing if USES does not contain pytho=
n.
--=20
Mathieu Arnold
--774jyfxxesn4kttv
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQKTBAABCgB9FiEEOraXidLtEhBkQLpbOkUW81GDzkgFAlwSJ8hfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNB
QjY5Nzg5RDJFRDEyMTA2NDQwQkE1QjNBNDUxNkYzNTE4M0NFNDgACgkQOkUW81GD
zkiowQ/9FTHeiVGw+h5Sh2niekymCawZVIH35SZv+WWsl+qjsj/xIMatXo9olJUq
rPjAz/LTx/3Yc7I37yVVvj63k6q6MEHfvFyPijRyBGmpWvxk1ENWhk7xCk1SAP1i
Vss7qN97oYqCN1HBcQ+hDtAMcX2F9L+XitQzFpZMhKOeGIpzhj3uEB+dLB5E/LdJ
hXNXgg9Ajky9biNoa9rj9bXPheIlPKOh//IcYPAqh6IBuz9oOavY5efrvb4fCR4o
ZQd4LShQpQP+8TBxLdiqLurAXLStMlUkZRsXxTqE64hrNdU+O31givnONMp+txXJ
txy70drC/q7yaoL9aHftvoPxBxjdSi2xaS3mP9m04trtXXCPu8+rWbajEq/e4qeh
Qyutp7dHGk75Miz/HWUYcpvUu30esqcRH05hlAMlwlQsurB6T29ph+TjGjeJP4YY
104dEvLJYFc2xpTastPL7oKkXKLrxNg/tBpDNE3BdFMCkGGKngv4L7qzkgeFpVrH
V3raGLXnY66GKuwIv+H8gJ3QMOlV5XcGVUPw/yQAnsFo4HmjLprkaSR3BpNm0bHY
rluuvo2ru4+Ic7n3Cv3mxtn19kSjAOJwHHh9Wc7KC7JbmcLtdBjgwkf81DMmej7d
Xgf0eQsqBNBkADg13LxxaUowJf19/Vd/TsYTxAse3LJVSBPFFVM=
=HkMz
-----END PGP SIGNATURE-----
--774jyfxxesn4kttv--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181213093504.vwene4mp5cy5ehgd>