[chirp_devel] Questions regarding packaging

[Dan Smith]

> 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?

Because it's half-baked, untested, and probably brokenish. I used to use
it a lot before I built the developer tools into the UI. I'd love for it
to get more attention and be a useful thing for people to use for
automation and stuff. However, it's almost completely ignored at the
moment. I wouldn't recommend including it in packages in its current state.

--Dan