You'll want to use this trick: <https://trac.macports.org/wiki/PortfileRecipes#fetchwithgetparams>
That will also allow you to set a filename that contains a version, simplifying things when the file is updated. So the master_sites entry will be 'https://gitlab.gnome.org/GNOME/libhttpseverywhere/-/raw/9c43785fe5ce13c70b8a1abfece834d12fc9d0fb/data/default.rulesets?inline=false&dummy=' and the distfiles entry will be something like 'default.rulesets-2019.1.7'. (Use a tag so fetch attempts for this distfile only use its own master_sites URL.) - Josh On 2020-10-24 09:59 , Chris Jones wrote: > > I would avoid directly linking to a file in the master branch, as thats > a moving target, so could change at any point. Instead link to a > specific commit version, e.g. > > https://gitlab.gnome.org/GNOME/libhttpseverywhere/-/blob/9c43785fe5ce13c70b8a1abfece834d12fc9d0fb/data/default.rulesets > <https://gitlab.gnome.org/GNOME/libhttpseverywhere/-/blob/9c43785fe5ce13c70b8a1abfece834d12fc9d0fb/data/default.rulesets> > >> On 23 Oct 2020, at 7:22 pm, Ken Cunningham >> <ken.cunningham.web...@gmail.com> wrote: >> >> The file is here, it seems: >> >> https://gitlab.gnome.org/GNOME/libhttpseverywhere/-/blob/master/data/default.rulesets >> >> >>