Bug#380173: ITP: deb822 -- Read and manipulate RFC822-like files (e.g. .dsc and .changes)
Package: wnpp
Severity: wishlist
Owner: John Wright <john@movingsucks.org>
* Package name : deb822
Version : 0.1
Upstream Author : Dann Frazier <dannf@debian.org>
* URL : http://free.linux.hp.com/~jswright/deb822/trunk
* License : GPL
Programming Lang: Python
Description : Read and manipulate RFC822-like files (e.g. .dsc and .changes)
deb822 abstractifies the RFC822 format used in Debian's control files. You
can use a deb822 object like a Python dictionary, referring to control fields
as dictionary keys.
.
deb822 also has some convenient features that arespecific to Debian's .dsc
and .changes files. It was originally written for the packaging of
SystemImager, in order to merge multiple .changes files. It can also give
you a list of all the files mentioned in a control file in a convenient form.
Naturally, the binary package would be named python-deb822. This is a
polished version of dannf's deb822.py module he uses for SystemImager
packaging and for kernel.debian.net's archive. We agreed that it should
be Debian-native, and that I could maintain the package. (I'm not sure
if an ITP is technically required for Debian-native packages, but I'm
submitting this to be safe, and to get feedback.)
The URI above is actually a bzr (Bazaar-NG) branch. Note that the
"working tree" doesn't automatically get updated, so the files you see
there when using a web browser may be out of date. To check out the
current source, please use bzr:
$ bzr branch http://free.linux.hp.com/~jswright/deb822/trunk deb822
It's just about ready to be uploaded. If you have any suggestions
before then, please let me know. A link to a bzr branch would be
preferred for code changes, but a diff is, of course, welcome.
Thanks,
John Wright
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Reply to: