[chirp_users] What's next for CHIRP

[Greg Troxel]

Dan Smith via chirp_users <chirp_users at intrepid.danplanet.com> writes:

> I'd like to announce the availability of what I'm calling the
> "CHIRP-next" build for the new year. If you're not aware, some of the
> libraries that CHIRP depends on have been orphaned such that CHIRP was
> a bit stuck in time for many years. Overcoming this obstacle required
> a lot of changes to CHIRP's core, drivers, and the GUI has had to be
> completely rewritten as a result. This has been a ton of work, and we
> still have a lot left to do.

I maintain the chirp package in pkgsrc.  So far I haven't dug in to
CHIRP-next but I've been silently cheering you on; chirp is one of the
last 3 programs on my system to need python2.7.

What is the transition plan?  Is CHIRP-next a branch in the repo, and
when it works well enough it will be merged, and hence the chirp daily
snapshots (with YYYYMMDD) will then be python3?  If so, that's great and
I will simply adjust the package.

Or, is chirp going to remain python2.7 and basically not get updates,
and I should create a packge for CHIRP-next which will remain as the
name, with the current distribution tarball location, even after next
becomes the standard approach?

Or, something else?

73 de n1dam