From owner-freebsd-ports@freebsd.org  Thu Dec  6 19:31:26 2018
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 515ED1310363
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Thu,  6 Dec 2018 19:31:26 +0000 (UTC) (envelope-from freebsd@grem.de)
Received: from mail.grem.de (outcast.grem.de [213.239.217.27])
 by mx1.freebsd.org (Postfix) with SMTP id 44CEF7C547
 for <freebsd-ports@freebsd.org>; Thu,  6 Dec 2018 19:31:25 +0000 (UTC)
 (envelope-from freebsd@grem.de)
Received: (qmail 70971 invoked by uid 89); 6 Dec 2018 19:31:24 -0000
Received: from unknown (HELO ?100.89.69.208?) (mg@grem.de@109.41.193.240)
 by mail.grem.de with ESMTPA; 6 Dec 2018 19:31:24 -0000
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: Best way to deal with .pyc files?
From: Michael Gmelin <freebsd@grem.de>
X-Mailer: iPhone Mail (16C50)
In-Reply-To: <f2c1b368-cd2e-85a3-a5c7-794d69204625@FreeBSD.org>
Date: Thu, 6 Dec 2018 20:31:23 +0100
Cc: FreeBSD Ports <freebsd-ports@freebsd.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <65A6C774-6F62-4385-9DB9-EF0F359CEE4A@grem.de>
References: <f2c1b368-cd2e-85a3-a5c7-794d69204625@FreeBSD.org>
To: John Baldwin <jhb@freebsd.org>
X-Rspamd-Queue-Id: 44CEF7C547
X-Spamd-Result: default: False [-0.56 / 15.00]; ARC_NA(0.00)[];
 RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.85)[-0.850,0];
 FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[];
 NEURAL_HAM_LONG(-0.79)[-0.793,0]; MIME_GOOD(-0.10)[text/plain];
 DMARC_NA(0.00)[grem.de]; AUTH_NA(1.00)[];
 RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[];
 TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[mx.grem.de];
 RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.82)[-0.817,0];
 R_SPF_NA(0.00)[]; RCVD_NO_TLS_LAST(0.10)[];
 FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[];
 SUBJECT_ENDS_QUESTION(1.00)[];
 ASN(0.00)[asn:24940, ipnet:213.239.192.0/18, country:DE];
 MID_RHS_MATCH_FROM(0.00)[];
 IP_SCORE(-0.59)[ipnet: 213.239.192.0/18(-0.43), asn: 24940(-2.50),
 country: DE(-0.01)]
X-Rspamd-Server: mx1.freebsd.org
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Dec 2018 19:31:26 -0000



> On 6. Dec 2018, at 19:21, John Baldwin <jhb@freebsd.org> wrote:
>=20
> 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 .pyc fil=
es in
> those directories that are not deleted by 'pkg delete'.  What is the best w=
ay to
> handle this case?  Should the pkg-plist include @rmtry entries for each py=
c
> file or is there a better way?

Pre-generate the pyc files on package build and install them with the port, s=
o they become part of plist (there are examples of that in the ports tree, w=
henever possible for both py27 and py3x).

Best,
Michael


> --=20
> John Baldwin
>=20
>=20
> _______________________________________________
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"