does libhttpseverywhere have to have a 7MB uncompressed file of rules in the files dir?

Ken Cunningham ken.cunningham.webuse at gmail.com
Sat Oct 24 01:48:12 UTC 2020


Thanks for all that.

I gave it a shot here <https://github.com/macports/macports-ports/pull/8917 <https://github.com/macports/macports-ports/pull/8917>>

Ken


> On Oct 23, 2020, at 5:20 PM, Joshua Root <jmr at macports.org> wrote:
> 
> 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.webuse at gmail.com> wrote:
>>> 
>>> The file is here, it seems:
>>> 
>>> https://gitlab.gnome.org/GNOME/libhttpseverywhere/-/blob/master/data/default.rulesets
>>> 
>>> 
>>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20201023/2845b19c/attachment-0001.htm>


More information about the macports-dev mailing list