Can you make a tagged release?

[Joseph Fowler]

Hi Lucas. Joe here. I’m the MacPorts maintainer for the demeter package, and I want to start using Larch as its backend instead of the old, deprecated predecessor (ifeffit). But Larch relies in turn on PeakUtils. Great, right? I can just make a new py-peakutils package for MacPorts.

I cannot get it to work, though. I believe MacPorts cannot use this package because it doesn’t have any releases, or any tags. (One or the other.)

I see that you have version numbers, most recently 1.3.2. Would you consider tagging one or more commits and using the Bitbucket release process? I don’t remember how that works, but I have done it before. I know it’s pretty easy. I think you want to tag f1f26011 as “v1.3.2”.

[Lucas Hermann Negri]

Hi, Joe. Done (v1.3.3).

[Joseph Fowler]

Brilliant. I am now in possession of the world’s only MacPorts installation of PeakUtils!

Of course, I’ll share it with the world soon enough. Larch is a big problem, though. It might be days or weeks before the whole project, including PeakUtils, is a part of the public MacPorts system. Or the MacPorts people might reject this entire project, who knows? I'm not very adept with the MacPorts culture, so even if they welcome this contribution, it might take me a while to figure out the process.

Either way, I appreciate your help and quick response.