Debian packaging

I have been thinking about producing the a-a-p package and getting it into
the Debian distribution.  The work is going well; I already have a working
package that passes lintian.  I don't want to duplicate anyone's work, so
if the list knows that someone else has already started a Debian package
I'll stay out of the way.  Otherwise I'll go ahead and ITP it, since
nobody else has done that.

Some random points: 

* I don't intend to package agide, since I don't use it.

* I intend to package A-A-P pretty much the way ./aap install installs it,
with some minor differences to conform to Debian spec:
  - There is no Exec-* directory.  The python files go into /usr/lib/aap. 
It would make my job as packager easier if there was a LIBDIR option I
could pass in.  Ideally, $PREFIX/$LIBDIR/__init__.py exists.
  - The doc is a separate package, since it is substantial.  To do this I
have to install and then move the docs out of the package directory.  I
see that there is a FULLDOCS option, but there isn't an ONLYDOCS option. 
If there were, I could 
./aap install FULLDOCS=no PREFIX=$CURDIR/debian/aap/usr LIBDIR=lib
./aap install ONLYDOCS=yes  PREFIX=$CURDIR/debian/aap-doc/usr \ 
              DOCDIR=share/doc
And, tada!  Everything's where it belongs.
  - I have to recreate the symlink to aap every time.  It would be a
little easier to maintain the package if the symlink was a relative path,
to 
  "../%s" % LIBDIR # assuming it's being installed in $PREFIX/bin
  - I have to move the man page.  It normally goes into $PREFIX/man.  I
move it to $PREFIX/share/man, per FHS.  This is inconvenient; can I get a
MANDIR option, similar to DOCDIR and LIBDIR?

... note that none of the above are showstoppers.  I have already worked
around all of them in my debian/rules; they are simply conveniences so I
can get future versions of the package out a little faster as upstream
versions appear.  New versions of aap seem to appear every week so every
little bit makes a difference!

* It is not going to be installed as a Python package.  Nothing ends up in
/usr/lib/python*

* It Suggests: aap-doc.  It could also suggest agide, if there were
someone willing to package it.

* I am incidentally also a wiz with Inno Setup.  It'd be quick work for me
to produce a Windows self-installing exe for AAP just as I do the debian
packages, and even use Inno to adjust PATH appropriately during the
install.

Any thoughts?  Ideas?  Things I need to take into account?

C

__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf