Re: Bug#128531: tmda
>
> Any policy that forces me to compile .py{c,o} object files in my postinst is
> braindead. Then I also have to delete them in purge/postrm, and the
> packaging system knows nothing about them.
>
A program run by a user will never be able to write out the .py[co] files so
the files MUST be generated by the postinst which has root privs. Also we can
not expect the user to be running /usr mount rw except when a package is being
installed. So even if the user is logged in as root they will still be unable
to write the optimized files out.
What do you have against giving the user optimizations?
Reply to: