]> code.ossystems Code Review - openembedded-core.git/commit
distutils.bbclass: don't delete .pyo files
authorAndreas Oberritter <obi@opendreambox.org>
Mon, 21 May 2012 20:54:23 +0000 (22:54 +0200)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Thu, 24 May 2012 07:34:50 +0000 (08:34 +0100)
commit25e186ad5b75bd2f93435857580bd16698e18e21
tree928a28e4a5da04ce6e23d0c7c585c40563e42964
parentfaca42ee5249cf6aae9e53e44bb404de21dd4471
distutils.bbclass: don't delete .pyo files

* Deleting .pyo files causes them to get compiled on the target.
* First boot gets *really* slow for python based projects.
* No space gets saved on the target.
* The package manager doesn't know about the files and
  therefore fails to uninstall them, occupying space and causing
  uninstalled python scripts to remain executable.
* It's inconsistent, because python itself and autotools based
  projects already ship .pyo files.
* Probably .pyo files were deleted because .pyc files were
  available earlier, but this has changed and OE-Core's python
  now only generates optimized .pyo files. Deletion of .pyo was
  introduced in 2008, python/04-default-is-optimized.patch
  was introduced in 2009.

Signed-off-by: Andreas Oberritter <obi@opendreambox.org>
meta/classes/distutils.bbclass