Hi Greg,
thanks for your quick reply.
On Sun, Jul 22, 2012 at 07:13:39PM -0700, Greg Caporaso wrote:
> Thanks for getting in touch about this. The biom-format project is
> under GPL. I'll also make sure that we drop the OS X files next time
> we do a release build.
Thanks, droping those files makes life a bit easier. I'd also recommend
to include some COPYING file into the archive.
When trying to build the package for Debian one question occured to me:
There is a dir python-code/support-code containing C++ code which does
not seem to be really used because when executing `python setup.py` this
is not touched. I wonder what role this code might play. The
background of my question is that if I have a pure Python package it
would be Debian architecture 'all' - otherwise the package would need
to be (auto)builded for all Debian release architectures which would be
not be needed if you would confirm that the sparsemat lib is not used.
One final remark: There will be four files installed to /usr/bin which
are all featuring the *.py extension. Please consider droping this
extension - reading [1] and [2] might give you good reasons to do so.
Kind regards
Andreas.
PS for Debian Med team: The packaging is close to finalised at
Vcs-Svn:
svn://svn.debian.org/debian-med/trunk/packages/python-biom-format/trunk/
We should probably also build the docs as described in INSTALL and
some manpages would be great.
[1] http://en.wikipedia.org/wiki/Filename_extension#Command_name_issues
[2]
http://www.talisman.org/~erlkonig/documents/commandname-extensions-considered-harmful
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120723081158.ga8...@an3as.eu
