> > The entry point is generated by 'setup.py install_scripts', which is > > executed by pybuild after files specified in *.install have been > > installed (correct me if I'm wrong). > > I haven't demonstrated for this case, but I would be surprised if that's > how it behaves. To my mind the ‘setup.py install’ command (and hence the > ‘… install_scripts’ command) should be part of the ‘dh build’ sequence. > > Again, someone should correct me if I'm wrong.
Hum, the build logs suggest that ‘setup.py install’ is ran during the
‘dh binary’/‘dh_auto_install’ sequence. Concerning the order of execution
in dh_auto_install, you're true: In fact, the files specified in
debian/*.install are installed after ‘setup.py install’ have been executed.
However, it seems that setup.py is directly installing the entry point without
storing a copy of it in the current directory, so anyway I don't see how I
could install the entry point in the application package via a debian/install
file[0].
So the question would rather be: how can I properly ask pybuild (setup.py ?)
to install the entry point in the application package (slugify) instead of
installing it in the library packages (python{3}-slugify) ?
[0] and, even if I could do it, I think I would still have to override
dh_auto_install to remove the installed entry points from the library packages,
which I originally wanted to avoid. :)
--
Hugo Lefeuvre (hle) | www.owl.eu.com
4096/ ACB7 B67F 197F 9B32 1533 431C AC90 AC3E C524 065E
signature.asc
Description: PGP signature
