[chirp_devel] Questions regarding packaging

[David Thurstenson]

Hi,

I manage chirp-hg on the Arch User Repository[1], and there has been
some discussion about how things should be packaged going forward.

My main question is regarding chirpc. I'm aware that the release
tarball (chirp-daily-20170406 as of the time of writing) does not
currently include chirpc and it's documentation, but I'm not clear on
why. What is the reason for it's exclusion?

I ask as we are deciding whether or not to include chirpc in the
release package. The Arch Packaging Guidelines for Python packages[2]
strongly suggests using the setup.py installer that is released by
upstream, and the exclusion of chirpc from this installer seemingly
indicates that it shouldn't be included in a downstream package. Since
some users might like the option of using chirpc, I want to include
it, but if it's not release-worthy, I'll include it as a separate
optional package instead.

Thanks,
David

[1]: https://aur.archlinux.org/packages/chirp-hg/
[2]: https://wiki.archlinux.org/index.php/Python_package_guidelines