building ungoogled-chromium from ports

AlfredoLlaquet said:
why ungoogled-chromium is not part of the packages remains a mystery. Maybe there are insidious interests at play. I prefer to believe there are not.
Click to expand...
You have the reason in the OP. It's because it chokes up the process of building packages. It's one of the "heaviest" packages out there. On the machine that builds 15.0 packages, it took almost 25 hours to build the regular Chromium. On the machine that builds for 14.3, it took 36 hours if memory serves me well. And don't forget these programs are constantly changing, so their packages must be built every single time. Firefox and derivatives such as Waterfox "only" take a "few hours" in comparison and are usually both available, bar some unfortunate mishap.

jmos said:
the label "ungoogled" on it isn't trustworthy to me - it's far too much code from a company that isn't acting in my interests at all; I only use that browser for testing, and not for everyday use.
Click to expand...
At a certain point you have to put your trust somewhere. Why do you trust FreeBSD? If you don't trust Ungoogled-Chromium, do you trust Chromium on which it is based? Unless you have the time and skills to program your own operating system, desktop environment, window manager, file manager, multimedia player, web browser, etc. you have to rely on what others provide you. Do you trust the compiler used to build ports on your own machine? Do you trust the BIOS/UEFI? Do you trust the firmware that runs your CPU, HDD, NIC, BT, etc.?
Just saying...

jmos said:
And I use VMs as well as different user accounts.
Click to expand...
Both of which are great for system-level isolation only but don't do much to protect you against any other threat.

Do you trust your ISP?
Do you trust your government?
Do you trust commercial entities?
Do you trust governments that are allied with your government?
Do you trust governments that are hostile to your government?
Do you trust whoever is managing and maintaining your city's networking/phone/cable infrastructure?
Do you trust the firmware running your hardware?
Do you trust your VM?
Do you trust the code that runs on the websites you are visiting? Even if you answered all the above with "yes", what if that website was compromised by some third-party hack? Phishing/social engineering? Cross-Site Request Forgery? Cross-Site Scripting? DNS Poisoning?

The world is a dangerous place, but as I said: at a certain point you have to put your trust somewhere.
 
Beastie said:
You have the reason in the OP. It's because it chokes up the process of building packages. It's one of the "heaviest" packages out there. On the machine that builds 15.0 packages, it took almost 25 hours to build the regular Chromium. On the machine that builds for 14.3, it took 36 hours if memory serves me well. And don't forget these programs are constantly changing, so their packages must be built every single time. Firefox and derivatives such as Waterfox "only" take a "few hours" in comparison and are usually both available, bar some unfortunate mishap.
Click to expand...
Thank you for your explanation. I guess you speak from having direct knowledge of that being the reason. Maybe whoever decides this things could opt for building ungoogled-chromium and not chromium.
 
Everything , from kernel , packages ,too my shoes an underwear. Yes for real devs they smell bad. But I'm working on it. One exception zed editor. 16GB is to little to compile.
 
Alain De Vos said:
Everything , from kernel , packages ,too my shoes an underwear. Yes for real devs they smell bad. But I'm working on it. One exception zed editor. 16GB is to little to compile.
Click to expand...
Please know that I don't follow almost any thread, so if you want that I get notified about any of your answers to my mighty person (which you may not want) you need to click reply or quote, which doesn't guarantee that I read them, anyhow, because I'm very selective in what I choose to read.
 
You must log in or register to reply here.
Back
Top