Hi again, I made some more progress on packaging HTSeq.
* I switched to git-buildpackage style packaging. * Its now installing the user scripts into /usr/bin * It now builds (and installs!) man pages for the * Upstream claims the main purpose of HTSeq is to write your own analysis scripts. so I think the name python-htseq makes sense. * Lintian is only complaining about spelling errors and I'd like to wait to fix those by working with upstream. I replaced the previous bare-packaging git repository with the gbp style one at https://github.com/detrout/python-htseq. If that looks decent I can push to alioth. Diane On Friday, July 26, 2013 10:48:38 Andreas Tille wrote: > Hi again, > > (sorry for the full quote below but my mail below did not reached the > list for whatever reason ...) > > I had another thing to consider: The soure tarball of python-htseq > contains two scripts in scripts/ directory. If I'm not totally > misleaded these are the user interface to the Python code end should be > installed to /usr/bin ... or at least to /usr/share/doc/<pkg>/examples. > In the first case please use help2man to create some simple manpage > (we have examples for instance in packaging of last-align). > > Moreover if you consider these scripts as the main interface for the > package which makes it kind of a user application rather than a Python > module there is no real point in naming the package python-htseq. > Finally it does not matter for the user in what language some software > is written in and thus a simpla htseq would perfectly do. > > Kind regards > > Andreas. -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/3847860.rL4gihJAFj@myrada
