[Neurodebian-devel] Uploading pyqtgraph packages

[Yaroslav Halchenko]

On Tue, 14 Jan 2014, Luke Campagnola wrote:
>      [2]https://github.com/neurodebian/neurodebian/tree/master/tools

>    I'll have a look..  Can't promise any quality documentation, but I usually
>    find that having someone else send a crappy pull request is enough
>    motivation for me to fix it properly :)

I am efficient in review (which is different from "taking over" ;)) 

>      BTW -- have anyone looked/used [3]http://docopt.org/ ? -- looks very
>      interesting for quick cmdline interfaces, but docopts for bash seems to
>      be not
>      in debian... oh well

>    It's all of one python
>    file: [4]https://github.com/docopt/docopt/blob/master/docopt.py
>    Just include it in the neurodebian-dev :)

well -- this one is for Python.  Those little scripts are bash, for that
docopts would be needed  to complement docopt.py -- that would make it
TWO! and come on -- we are the Debian guys, nothing should get bundled
like that! ;)

>      >    From there you can run `python setup.py sdist deb
>      --force-version=0.9.8`.
>      >    The 'deb' command just creates a deb_build directory and populates
>      it with
>      >    the necessary pieces before calling `dh -us -uc`.

>      brrr ;-)  why not just debian/ directory?  your setup would
>      complicate contributions from debian folks etc... you would need to
>      provide
>      us the generated source package anyways.  I would recommend just
>      carrying debian/ and using git-buildpackage

>    I like to keep the package root as clean as possible. For a package that
>    claims to run on all flavors of windows, osx, and linux, it doesn't make a
>    lot of sense (to me) for 'debian' to appear at the root.  Can you give
>    examples of how this complicates contributions from debian folks? In any
>    case, at least the changelog needs to be generated, so *some* command must
>    be run. 

it doens't have to be anywhere actually.  You would just need a separate
branch -- e.g. debian -- where you will keep your packaging.
I believe I had some arguments for docker.io guys somewhere.. e.g.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706060#30


>    I'll have a peek at git-buildpackage. I see it can build changelogs from
>    the commit history, but I'm pretty skeptical this would generate an
>    acceptable result..

it is actually quite neat, but I moved away from this auto-changelog
generation.  I am not that feature-based-committer.  Otherwise changelog
becomes no better than dumps of git log -- require work to make them
digestable

>      back to cows:
>      btw -- in generated debian/control dh-python is missing from
>      build-depends
>      and as I said those debian/*install  should not be needed in this case
>      iirc.

>      so here is a PR
>      [6]https://github.com/lcampagn/pyqtgraph/pull/4

>    I had tried adding dh-python to my build dependencies before and I get
>    "dpkg-checkbuilddeps: Unmet build dependencies: dh-python". I'm not sure
>    what to make of that, since dh_python commands are provided by the core
>    python package.

it is about pybuild not dh_* commands

if you get back to stock dh_* commands, there might be a bit more work
todo manually in debian/rules for python3 support etc, but not
rocket science really.

which distribution release you are using anyways?

-- 
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Senior Research Associate,     Psychological and Brain Sciences Dept.
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834                       Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik