the future of port:audacity

[Dave Allured - NOAA Affiliate]

So *that's* what I was missing.  Ouch.


On Mon, Feb 13, 2023 at 1:54 PM Clemens Lang <cal at macports.org> wrote:

> Hi again,
>
> On Mon, Feb 13, 2023 at 07:43:43PM +0100, Clemens Lang wrote:
>
> > On Sun, Feb 12, 2023 at 01:53:20PM -0500, Dave Allured - NOAA Affiliate
> via macports-users wrote:
> > > I looked at the Audacity website, https://www.audacityteam.org .  It
> > > looks like Audacity is in robust current maintenance, sources are
> > > available, and legacy and modern Mac OS versions are supported through
> > > Ventura and Intel/M1/M2.  The current release is 3.2.4, almost two
> > > years ahead of the version cited by René.  You said this is in limbo?
> > > What am I missing?
> >
> > We should probably consider moving to Tenacity, as upstream Audacity has
> > recently taken a few decisions that are questionable.
> >
> > See [1] for more details on this and the current Tenacity source code.
> > Ideally, we'd add a new tenacity port and possibly mark audacity as
> > replaced_by tenacity, or at least add a note about this.
> >
> >   [1]:
> https://codeberg.org/tenacityteam/tenacity/src/branch/main/README.md#user-content-motivation
>
> Actually re-reading some of the upstream tickets referenced there, the
> audacity developers seem to have taken the feedback they received on
> these changes seriously, so maybe the situation isn't as bad as I made
> it out to be.
>
> Something to be aware of regardless, but please do check upstream
> sources and come to your own conclusions.
>
> --
> Clemens
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20230213/e236fbcf/attachment.htm>