I and a few others are working on updating the chirp package in pkgsrc
from the last release to a daily snapshot. That caused me to look at
our package, and I see that it depends on py-gtk2, which in pkgsrc is
marked as python 2.7 only. In general we're trying to have packages be
able to build wi
"Glenn K0LNY" writes:
> Finally, someone who understood my question.
> So the answer might be that the inability to keep up with dependencies would
> keep it from the distro's main repository?
> This is sort of what I was guessing, but wanted to make sure.
As a meta point, and coming from some
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
I know this project doesn't believe in releases, but pkgsrc currently
provides a package with a date as the version. Because chirp-next is
labeled next, we are still providing the old codebase, which has not
seen an update in a long time.
Should we consider the latest chirp-next to be the releaes
Dan via chirp_users writes:
Thanks for the quick reply.
> I’ll answer that by quoting directly from yesterday’s release email:
>
>> Unless you have a reason not to, we recommend using the latest build of
>> CHIRP-next at all times.
>
> And from the download page:
>
>> The CHIRP team recommends
Dan via chirp_users writes:
>> Not important, but I wonder if next going to remain "next" indefinitely.
>> It sort of implies "this is a beta towards a future release”.
>
> Originally I said the plan would be to start calling it daily again,
> but I think it’s probably best to just drop the -next
