Hi Dominik, thanks for your reply. > Well, in that case, with you being upstream, I'd separate the two > packages entirely.
Yes, I can do that. But, don't you think a whole package for a single python file is... too much? >> I can exclude rpi.py module from main package and create a >> python3-mypackage.rpi.install >> file installing rpi.py in /usr/lib/python3/mypackage but I don't think it is >> the right way of doing that. > > Why not? Because I'll miss all the "egg"-related files. Won't I? And, how can I choose the right destination folder? /usr/lib/python3 or /usr/lib/python3.4 perhaps? > This is not a Python package. > > (Hint: no __init__.py…) Of course there is a __init__.py file with all the required import inside mypackage/ folder. I forgot to mention. >> The MANIFEST.in >> > include setup.py >> > include MANIFEST.in >> > recursive-include mypackage *.py >> > include bin/mydaemon > > Uh? All of this is duplicating setup.py. Just remove it. Ok, you are right. > Instead, please > make sure to include your full licence, readme and changelog in the > source tarball from within MANIFEST.in. Yes yes, the whole file include README.md, COPYING, CHANGELOG and a samples folder. Thanks, bye Simone
