[chirp_devel] Questions regarding packaging
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
On Wed, Apr 19, 2017 at 7:19 AM, David Thurstenson via chirp_devel chirp_devel@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
* On 2017 19 Apr 10:27 -0500, Tom Hayward via chirp_devel wrote:
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.
I did use it in an attempt to figure out the Alinco DR-635T a year or so ago as I recall. I think I got it from the Git repository, however.
73, Nate
On Wed, Apr 19, 2017 at 3:09 PM, Nate Bargmann via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
I did use it in an attempt to figure out the Alinco DR-635T a year or so ago as I recall. I think I got it from the Git repository, however.
What Git repository?
Tom
* On 2017 19 Apr 17:31 -0500, Tom Hayward wrote:
On Wed, Apr 19, 2017 at 3:09 PM, Nate Bargmann via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
I did use it in an attempt to figure out the Alinco DR-635T a year or so ago as I recall. I think I got it from the Git repository, however.
What Git repository?
SVN, then. :-)
I'm just used to nearly everything being in Git that I typed it without further thought.
73, Nate
On Wed, Apr 19, 2017 at 5:07 PM, Nate Bargmann n0nb@n0nb.us wrote:
- On 2017 19 Apr 17:31 -0500, Tom Hayward wrote:
On Wed, Apr 19, 2017 at 3:09 PM, Nate Bargmann via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
I did use it in an attempt to figure out the Alinco DR-635T a year or so ago as I recall. I think I got it from the Git repository, however.
What Git repository?
SVN, then. :-)
I'm just used to nearly everything being in Git that I typed it without further thought.
At one point I think someone imported the Chirp hg repo into Github. I thought maybe you were referring to that.
The official repo is http://d-rats.com/hg/chirp.hg.
Tom
* On 2017 19 Apr 19:16 -0500, Tom Hayward via chirp_devel wrote:
At one point I think someone imported the Chirp hg repo into Github. I thought maybe you were referring to that.
The official repo is http://d-rats.com/hg/chirp.hg.
Mercurial popped in my mind after I sent that. Next time I should look first.
73, Nate
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
participants (4)
-
Dan Smith -
David Thurstenson -
Nate Bargmann -
Tom Hayward