Follow

Inspired by the thread below and after responding that open source needs devs more than money, I've started the process to setup dev environments for Chromium and Firefox. So far, it looks like I need 30gb of space for Firefox and ?? for Chromium.

I've been downloading source code I guess using Google's depot tool for the last hour. I only know that I was warned to make my Mac not shut off if the screen does because there will be some long running network connections.

On the bug reporting side, both have their very highly-populated bug trackers though I give Firefox props for having a first-issue focused one called Codetribute.

30+??? GB is too much, even the ?? might be too much so I'm setting up a VM with 250GB of disk on which I'll build Chromium if it won't work in 40.

Thread: shrike.club/@kate/106903417065

· · Web · 1 · 0 · 0

Chromium mac build instructions say:
Expect the command to take 30 minutes on even a fast connection, and many hours on slower ones.

I've been running this for 1.5 hours hitting speeds of 30Mbps regularly. Not sure if this is slow or fast but I'm seeing a git Receiving objects that's been stuck on 63% for a while.

Intresting. I like Mozilla's bootstrap.py in that it suggests and educates about a bunch of mercurial settings and extensions that I wonder about now for git.

And I can't believe I have a phabricator account again through Bugzilla. Feels like the last time I was in corporate dev, though I'm not sure the weekend hacker/student would enjoy yet-another-account.

Meanwhile the `fetch chromium` is giving alarming messages about fatal early EOF and index-pack failed. Still have 21gb of free disk space and internet has been fine so hopefully it retries. 🤷

Now that wasn't so bad honestly. I chose the Artifact mode which apparently downloads pre-built binaries for the c++ code. This one is apparently better for front-end/ui work. I wanted to start simple and now after `./mach run` I'm looking at a working browser (with the sponsored links that started all of this).

Two hours including a VM install isn't bad overall. Maybe I'll tackle one of the first bugs I saw in Codetribute.

In the mean time, Chromium's fetch continues...

Hello `fetch chromium` my old friend.

STIILL running after four and a half hours. Looks like you're done downloading and now "running hooks"... wasm_fuzzer, that looks interesting.

BREAKING NEWS

Subprocess failed with return code 2!

47GB of data on disk and we've run out of space. Will have to pick this up later in the VM.

Thanks for playing!

Sign in to participate in the conversation
Ecko / c4.social

Creating magic through evolution of the Fediverse. Running Ecko, a community-driven fork of Mastodon managed using the Collective Code Construction Contract (C4) by the Magic Stone Community. C4 is a protocol for asynchronous, non-blocking, distributed, problem-focused software development.