Hello Ralf, On Tue, Dec 22, 2009 at 10:48:22PM +0100, Ralf Wildenhues wrote: > > Now, how can I exclude the source .py files from the installation? I've > > tried nodist_nobase_python_PYTHON, but that doesn't seem to do what I > > want. > > nodist_ is to avoid distribution, that is, `make dist' putting the file > into the tarball. To avoid installation (which happens with `make > install'), replace `python_' (which denotes that this file belongs > installed in $(pythondir) with `noinst_'. Note that noinst_PYTHON files > will not be byte-compiled, though. Note that noinst_PYTHON files will > not be byte-compiled, though.
For now I "find $(DESTDIR) -name \*.py |xargs rm" in install-data-hook. One more question: Is there any special reason behind 1. install-nobase_pythonPYTHON being called from install-data-am? 2. Python files being first installed, and then compiled? As a naïve user with C background, I'd expect "make" to compile the files, "make install" -- to install. This way one could make nodist_ work, too. What do you think? With kind regards, -- Baurzhan Ismagulov http://www.kz-easy.com/
