Hi Ben, > > The package is originally requested as a Python module[2] and it seems > > clear to me that the whole thing is only useful as a library > > I don't understand this statement. If it is *only* useful as a library, > why install the command-line entry point?
Indeed, I though about that, but python-slugify has been developed as an application[0] so I think it's rather a bad idea to completely ignore the entry point, even if it's not really useful. I think upstream would disagree, too. In my opinion, better build a third package, even if it won't be used a lot. > Why not install the command by using the configuration files for > ‘dh_install(1)’; that is, specify in ‘debian/slugify.install’ the files > to install. 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). So, I think that what you suggest won't work unless I write my own entry point, install it via debian/slugify.install and ignore those generated by setup.py. I think this would be even dirtier than what I already done. ;-) [0] https://github.com/un33k/python-slugify -- Hugo Lefeuvre (hle) | www.owl.eu.com 4096/ ACB7 B67F 197F 9B32 1533 431C AC90 AC3E C524 065E
signature.asc
Description: PGP signature
