Opened 7 years ago

Closed 7 years ago

#56003 closed update (fixed)

audacity: Update to 2.2.2

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: RJVB (René Bertin)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: audacity

Description

audacity should be updated to the latest version:

$ port livecheck audacity
audacity seems to have been updated (port version: 2.2.0, new version: 2.2.2)

When you do, please remove the inaccurate comment that the port is using a release tarball (it's not; the developers don't offer them*), and remove the distname override and allow the github portgroup's default distname to be used; it works fine.

*Well, they don't offer any release tarballs on GitHub, only automatically-generated ones. They do offer presumably premade tarballs at http://www.audacityteam.org/download/source/ but the download URLs contain a parameter called expiretime which makes me think the links will expire, and we wouldn't want to use expiring links in MacPorts. If we could find a non-expiring source of those files, and if they're suitable (if they contain all the files you need), then we should use them, since they're xz-compressed and smaller.

Change History (3)

comment:1 Changed 7 years ago by RJVB (René Bertin)

This update has taken me way more time than it should have, because of a regression causing the build to fail.

I'm not even certain why I jumped in so quickly; in the future please provide arguments why a newer version is better and/or the upgrade urgent.

And if we really have to split hairs: the non-devel port grabs the tarball corresponding to a release version. A tarball containing a release is a release tarball AFAIAC, regardless of how it was made.

comment:2 in reply to:  1 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to RJVB:

This update has taken me way more time than it should have, because of a regression causing the build to fail.

I'm not even certain why I jumped in so quickly; in the future please provide arguments why a newer version is better and/or the upgrade urgent.

I merely noticed a new version was available so I filed a ticket. That's all.

And if we really have to split hairs: the non-devel port grabs the tarball corresponding to a release version. A tarball containing a release is a release tarball AFAIAC, regardless of how it was made.

GitHub offers four different types of file downloads; you can specify in the github.tarball_from option which type you want. Based on the string that appears in their URLs, I'm naming those types "archive", "tarball", "downloads" and "releases". Since you haven't specified github.tarball_from, you get the default, which is a "tarball" not a "release". This GitHub project does not offer any "releases".

comment:3 Changed 7 years ago by mojca (Mojca Miklavec)

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.