Zhenfu and Josh, thanks for explaining. Now I know what to watch out for next time.
On Fri, Feb 14, 2025 at 6:31 PM Zhenfu Shi <[email protected]> wrote: > A release tarball is like a release binary file where the dev creates > manually either with a script or by hand and uploads it to the release > page. This project does not have one, the two tarballs under the release > notes are automatically generated by GitHub and (I think) is what > `github.tarball_from tarball` will get you. > > Zhenfu > > On Feb 15, 2025, at 12:15, Dave Allured - NOAA Affiliate via macports-dev < > [email protected]> wrote: > > This project clearly provides a Github "Releases" page with tarballs > listed under each release. What do you mean by "This project does not > provide release tarballs"? You are probably right, but I need to better > under stand the mixed message here. Thank you for your advice. > > On Fri, Feb 14, 2025 at 6:12 PM Joshua Root <[email protected]> wrote: > There are no uploaded assets attached to that release; all that's listed > are the auto-generated tarballs. So you'll have to use 'archive'. > > On Fri, Feb 14, 2025 at 6:09 PM Zhenfu Shi <[email protected]> > wrote: > >> This project does not provide release tarballs. Others might, but may use >> non standard file names such that you need to change distname in your >> portfile. For this project, use `github.tarball_from archive`. >> >> Zhenfu >> >> On Feb 15, 2025, at 11:57, Dave Allured - NOAA Affiliate via macports-dev >> <[email protected]> wrote: >> >> I am trying to switch from "github.tarball_from tarball" to the >> recommended "releases". The original "tarball" setting works fine, but >> "releases" fails to download. The upstream release and my Portfile lines >> are: >> >> https://github.com/Unidata/netcdf-c/releases/tag/v4.9.3 >> github.setup Unidata netcdf-c 4.9.3 v >> github.tarball_from releases >> >> This makes a download URL which gets "Not Found": >> >> https://github.com/Unidata/netcdf-c/releases/download/v4.9.3/netcdf-c-4.9.3.tar.gz >> >> I tried many permutations of the numbering and prefix strategy, with no >> luck. Is this a bug in the github portgroup, or do I misunderstand how to >> specify the version number details with "releases"? Or something else? >> >> >
