On Sun, Aug 22, 2010 at 04:31:08PM +0200, Thomas Spura wrote:
On Sat, 21 Aug 2010 18:48:31 -0400
David Malcolm wrote:
[snip]
>
> So you'll need to update the %files for python3 subpackages, listing
> something like:
> foo/__pycache__
> to capture the directory and the bytecode files within.
Unfortunately there is sometimes also a __pycache__ directory in
%{python_sitearch} (etc...) - for example in python3-minimock:
Checking for unpackaged
file(s): /usr/lib/rpm/check-files
/builddir/build/BUILDROOT/python-minimock-1.2.5-5.fc15.noarch
error: Installed (but unpackaged) file(s)
found: /usr/lib/python3.2/site-packages/__pycache__/minimock.cpython-32.pyc
/usr/lib/python3.2/site-packages/__pycache__/minimock.cpython-32.pyo
Installed (but unpackaged) file(s) found:
/usr/lib/python3.2/site-packages/__pycache__/minimock.cpython-32.pyc
/usr/lib/python3.2/site-packages/__pycache__/minimock.cpython-32.pyo
I decided to *NOT* own the __pycache__ directory, because other python3
packages will have that directory too, so I _believe_ the main python3
package should own them, isn't it?
python3-minimock currently only owns:
%{python3_sitelib}/__pycache__/minimock*
Makes sense to me -- if python3 owns site-packages then it should also own
site-packages/__pychache__.
Spec updated and build queued.
-Toshio