[chirp_devel] Questions regarding packaging

[Tom Hayward]

On Wed, Apr 19, 2017 at 7:19 AM, David Thurstenson via chirp_devel
<chirp_devel at intrepid.danplanet.com> wrote:
> 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.

You're the first person I've ever heard mention chirpc. I don't think
anyone uses it. So I don't think anyone would miss it.

Do you use it? Does it function? Assuming it's functional I'd say it's
your call whether to include it or not. If it's neglected and broken,
don't include it.

Sorry if this isn't very helpful. I assumed it was better than no response.

Tom