Re: Tool support for private modules
Ben Finney <ben@benfinney.id.au> writes:
> How can I best conform to the [Debian policy for Python modules
> specific to a single package]?
As an example, here's a Python package I'm trying to get packaged for
Debian. (I am the upstream author of this one, but I'm interested in a
solution that *doesn't* involve significant changes to the upstream
code.)
<URL:http://cheeseshop.python.org/pypi/gracie/>
How should I modify 'setup.py' to allow binaries and modules for this
package to be installed properly, and have the programs continue to
find the modules?
How should I construct the command line for 'setup.py' when I create
the 'install-python%' target in 'debian/rules' for this package?
--
\ Eccles: "I just saw the Earth through the clouds!" Lew: "Did |
`\ it look round?" Eccles: "Yes, but I don't think it saw me." |
_o__) -- The Goon Show, _Wings Over Dagenham_ |
Ben Finney
Reply to: