[chirp_users] New chirp-next build

[donotreply]

Greetings,

A new build of CHIRP-next is available. This includes changes made directly to 
the tree since yesterday and may include additional features, bug fixes, etc. 
As a reminder, this is different from the "daily" CHIRP builds in that new 
development and features are happening here. It is the latest and greatest, but 
also may be less stable than the "daily" builds at this time. If it works for 
you, we recommend using CHIRP-next, but if your radio is not yet working on it, 
then you may prefer to use the "daily" builds for the time being.

You can get it from here:

http://trac.chirp.danplanet.com/chirp_next/

A list of changes since the last build are here:

Changes for Build #47
[3046399+kk7ds] Add radio override for set_memory() policy

[3046399+kk7ds] Fix pasting memories over top of immutable fields

[3046399+kk7ds] Make tests more tolerant of highly immutable mems

[3046399+kk7ds] Add GMRS channels to bandplan_na

[3046399+kk7ds] Adjust GMRS-V2 set_memory immutable policy___
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to arch...@mail-archive.com at arch...@mail-archive.com
To unsubscribe, send an email to chirp_users-unsubscr...@intrepid.danplanet.com
To report this email as off-topic, please email 
chirp_users-ow...@intrepid.danplanet.com
Searchable archive: 
https://www.mail-archive.com/chirp_users@intrepid.danplanet.com

Re: [chirp_users] What's next for CHIRP

[Greg Troxel]

Dan Smith via chirp_users  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 MMDD) 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
___
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to arch...@mail-archive.com at arch...@mail-archive.com
To unsubscribe, send an email to chirp_users-unsubscr...@intrepid.danplanet.com
To report this email as off-topic, please email 
chirp_users-ow...@intrepid.danplanet.com
Searchable archive: 
https://www.mail-archive.com/chirp_users@intrepid.danplanet.com