I've used the feedparser package as a starting point for packaging http://webpy.org/ #349763
I am new to python packaging and I'm a little concerned about this 'setup.py'. It duplicates debian/control. So whilst maintaining one I have to worry about keeping debian/control and that setup.py in sync. Argh! I'm not even sure *where* and *what* setup.py does with this values like keywords, platforms and classifiers *on a Debian system*. I think they aren't necessary, so can I do without it? ----- Forwarded message from Kai Hendry <[EMAIL PROTECTED]> ----- From: Kai Hendry <[EMAIL PROTECTED]> To: Joe Wreschnig <[EMAIL PROTECTED]> Subject: Re: Python packaging questions Date: Sat, 4 Feb 2006 01:15:06 +0900 Reply-To: Kai Hendry <[EMAIL PROTECTED]> X-Debbugs-No-Ack: please On 2006-02-01T11:43-0600 Joe Wreschnig wrote: > On Wed, 2006-02-01 at 22:38 +0900, Kai Hendry wrote: > > I am thinking of packaging a python library that doesn't have a setup.py > > Reading debian/rules, I *think* that setup.py copies feedparser into > > /usr/lib/python2.3/site-packages/ > > Am I correct? > > Could I substitute setup.py for a dh_install or something? > Tell upstream to use a setup.py. Doing this manually is unmanagable and > makes transitions needlessly difficult. I am having to come up with the setup.py as upstream seems uninterested. That setup.py contains an awful a lot of duplication of debian/control. Do you use any tools to keep them in sync? Update the version? I personally don't like it. ----- End forwarded message -----
signature.asc
Description: Digital signature
