Date: Thu, 6 Dec 2018 20:31:23 +0100 From: Michael Gmelin <freebsd@grem.de> To: John Baldwin <jhb@freebsd.org> Cc: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Best way to deal with .pyc files? Message-ID: <65A6C774-6F62-4385-9DB9-EF0F359CEE4A@grem.de> In-Reply-To: <f2c1b368-cd2e-85a3-a5c7-794d69204625@FreeBSD.org> References: <f2c1b368-cd2e-85a3-a5c7-794d69204625@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?65A6C774-6F62-4385-9DB9-EF0F359CEE4A>