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

[Ken Cunningham]

Thanks for all that.

I gave it a shot here >

Ken


> On Oct 23, 2020, at 5:20 PM, Joshua Root  wrote:
> 
> You'll want to use this trick:
> 
> 
> 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='
> 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
>> 
>> 
>>> On 23 Oct 2020, at 7:22 pm, Ken Cunningham
>>>  wrote:
>>> 
>>> The file is here, it seems:
>>> 
>>> https://gitlab.gnome.org/GNOME/libhttpseverywhere/-/blob/master/data/default.rulesets
>>> 
>>> 
>>> 
> 

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

[Joshua Root]

You'll want to use this trick:


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='
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
> 
> 
>> On 23 Oct 2020, at 7:22 pm, Ken Cunningham
>>  wrote:
>>
>> The file is here, it seems:
>>
>> https://gitlab.gnome.org/GNOME/libhttpseverywhere/-/blob/master/data/default.rulesets
>>
>>
>>

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

[Chris Jones]

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

> On 23 Oct 2020, at 7:22 pm, Ken Cunningham  
> wrote:
> 
> The file is here, it seems:
> 
> https://gitlab.gnome.org/GNOME/libhttpseverywhere/-/blob/master/data/default.rulesets
> 
> 
> 

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

[Chris Jones]

Works for me...

Chris

> On 23 Oct 2020, at 8:29 pm, Ken Cunningham  
> wrote:
> 
> as far as I can see, the one from the website and the one in the ports tree 
> are identical:
> 
> $ ls -la /Users/Shared/Downloads/default.rulesets.1 
> ./www/libhttpseverywhere/files/default.rulesets
> -rw-r--r--  1 root  admin  6992700 20 Jul 12:11 
> ./www/libhttpseverywhere/files/default.rulesets
> -rw-r--r--  1 root  admin  6992700 23 Oct 12:25 
> /Users/Shared/Downloads/default.rulesets.1
> 
> $ cmp /Users/Shared/Downloads/default.rulesets.1 
> ./www/libhttpseverywhere/files/default.rulesets
> 
> $ diff -u /Users/Shared/Downloads/default.rulesets.1 
> ./www/libhttpseverywhere/files/default.rulesets
> 
> 
> I guess I can just add it as a distfile and delete it from the ports tree...
> 
> Ken

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

[Ken Cunningham]

as far as I can see, the one from the website and the one in the ports tree are 
identical:

$ ls -la /Users/Shared/Downloads/default.rulesets.1 
./www/libhttpseverywhere/files/default.rulesets
-rw-r--r--  1 root  admin  6992700 20 Jul 12:11 
./www/libhttpseverywhere/files/default.rulesets
-rw-r--r--  1 root  admin  6992700 23 Oct 12:25 
/Users/Shared/Downloads/default.rulesets.1

$ cmp /Users/Shared/Downloads/default.rulesets.1 
./www/libhttpseverywhere/files/default.rulesets

$ diff -u /Users/Shared/Downloads/default.rulesets.1 
./www/libhttpseverywhere/files/default.rulesets


I guess I can just add it as a distfile and delete it from the ports tree...

Ken

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

[Ken Cunningham]

The file is here, it seems:

https://gitlab.gnome.org/GNOME/libhttpseverywhere/-/blob/master/data/default.rulesets

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

[Joshua Root]

It does seem like that really ought to be a distfile. Going by the
comment, it is a newer upstream version of the file. Surely it must be
available for download from somewhere. Worst case, it can be hosted on
GitHub in a separate repo.

- Josh

On 2020-10-23 20:08 , Christopher Jones wrote:
> Hi,
> 
> This file has annoyed me on a number of occasions. I work with a full
> git checkout and tend to use utilities like ‘git grep’ a lot, and this
> file often gets a hit in those searches, and due to its size spams the
> results rendering it almost impossible to view any after that file.
> 
> One option, if the port still needs to patch these rules, would be to
> store it compressed in git, and uncompress it on the fly during patching
> 
> https://github.com/macports/macports-ports/blob/6d838b9cdbde1c2704da396a95ab99222b8db2c6/www/libhttpseverywhere/Portfile#L50
> 
> 
> Chris
> 
>> On 23 Oct 2020, at 2:52 am, Ken Cunningham
>> > > wrote:
>>
>> The ports tree is getting bloaty as it is, but is is fairly egregious
>> bloat…
>>
>> ls -la
>> total 13680
>> drwxr-xr-x  5 root  wheel      160 22 Oct 18:46 .
>> drwxr-xr-x  4 root  wheel      128 23 Aug 15:39 ..
>> -rw-r--r--  1 root  wheel  6992700 23 Aug 15:39 default.rulesets
>> -rw-r--r--  1 root  wheel      664 23 Aug 15:39
>> patch-fix-typelib-generation.diff
>> -rw-r--r--  1 root  wheel      910 28 Jun 07:30 patch-vala-0.42.diff
>>
>>
> 

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

[Christopher Jones]

Hi,

This file has annoyed me on a number of occasions. I work with a full git 
checkout and tend to use utilities like ‘git grep’ a lot, and this file often 
gets a hit in those searches, and due to its size spams the results rendering 
it almost impossible to view any after that file.

One option, if the port still needs to patch these rules, would be to store it 
compressed in git, and uncompress it on the fly during patching

https://github.com/macports/macports-ports/blob/6d838b9cdbde1c2704da396a95ab99222b8db2c6/www/libhttpseverywhere/Portfile#L50
 


Chris

> On 23 Oct 2020, at 2:52 am, Ken Cunningham  
> wrote:
> 
> The ports tree is getting bloaty as it is, but is is fairly egregious bloat…
> 
> ls -la
> total 13680
> drwxr-xr-x  5 root  wheel  160 22 Oct 18:46 .
> drwxr-xr-x  4 root  wheel  128 23 Aug 15:39 ..
> -rw-r--r--  1 root  wheel  6992700 23 Aug 15:39 default.rulesets
> -rw-r--r--  1 root  wheel  664 23 Aug 15:39 
> patch-fix-typelib-generation.diff
> -rw-r--r--  1 root  wheel  910 28 Jun 07:30 patch-vala-0.42.diff
> 
> 



smime.p7s
Description: S/MIME cryptographic signature