master_sites and codeberg.org

[Dave Allured - NOAA Affiliate]

Raf, I can not directly answer your question about the download URL.
Recent work added a new codeberg portgroup to make this simpler.  I suggest
you see what was done in the portfiles for other recent codeberg ports:
 smake, star, cdrtools.  There are also a few older codeberg ports to
examine, pre-portgroup, if you wish.


On Wed, Jun 14, 2023 at 2:58 AM raf via macports-users <
macports-users at lists.macports.org> wrote:

> Hi,
>
> I have a Portfile question.
>
> I have the (possibly incorrect) impression that
> values in the list of ${master_sites} need to be
> URLs to a directory that can have a filename appended
> to it to download the distfile. Is that correct?
> Or can it be the URL to the distfile itself?
>
> I'm asking because I use the codeberg.org git repository site,
> and when you make a "release" there, you can attach a file
> such as your official distfile/tarball. But the URL for it
> looks like:
>
>   https://codeberg.org/attachments/<UUID>
>
> I'd like to put that in a Portfile, but I'm worried that
> macports will append "/${name}-${version}.tar.gz" and try
> to download that. If it does, that won't work. But if it
> just downloads the URL itself, it would work.
>
> Does macports work with URLs like this in ${master_sites}?
>
> cheers,
> raf
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20230614/2e4a00d7/attachment.htm>