[arch-dev-public] Python packaging policy

Aaron Griffin aaronmgriffin at gmail.com
Fri Dec 19 00:59:50 EST 2008

On Fri, Dec 19, 2008 at 12:59 AM, Aaron Griffin <aaronmgriffin at gmail.com> wrote:
> On Thu, Dec 18, 2008 at 7:28 PM, Allan McRae <allan at archlinux.org> wrote:
>> Well, the options I see are
>> 1) .pyc/.pyo files are created as part of packaging.  That way we just
>> rebuild the package if needed during an upgrade.
>> 2) .pyc/.pyo files are recreated on python/package update.  So, we would
>> have a pre_update script that finds all the .pyc/.pyo files, deletes them
>> and a post_update script that rebuilds them.  In this option, it would be
>> better if .pyc/.pyo files were not part of a package as I don't like one
>> package touching another packages files.
> The problem with option #2 is that those files are no longer tracked
> by pacman. Removing the package could still result in removal of those
> files, but it gets very ugly... it'd be nice if these files were
> tracked by pacman.

OMG you said that already... sigh

More information about the arch-dev-public mailing list