For a simple package, "pkgadd" puts files into the system, and "pkgrm"
removes those files.
But the "python" interpreter generates bytecode files (filename patterns
*.pyc and *.pyo) alongside the normal *.py files. So these files get left
behind when "pkgrm" is run, which is somewhat untidy and asymmetric.
Are there conventions in the "pkg" mechanism for handling these extra
*.pyc and *.pyo files? There are probably (at least) two issues:
1. pkgrm: how to remove these files that have magically appeared?
2. pkgadd: how to manage and acknowledge their automatic appearance (or
perhaps force their creation for an install-time run of python, so that
their appearance will not have been magic).
If there are established conventions that I can use, then I won't be
re-inventing the wheel.
: David Lee I.T. Service :
: Senior Systems Programmer Computer Centre :
: Durham University :
: http://www.dur.ac.uk/t.d.lee/ South Road :
: Durham DH1 3LE :
: Phone: +44 191 334 2752 U.K. :