On Thu, 15 Oct 2026 12:09:31 +0100
void <[email protected]> wrote:

> On Thu, Oct 15, 2026 at 12:15:23PM +0200, Thierry Thomas wrote:
> >And we have the same problem with chromium and its cousins (iridium,
> >etc.).
> >
> >The problem seems to be financial in nature: the compilation farm needs
> >more beefy computers to build these packages!
> 
> Maybe a dedicated builder machine for huge things that can build at the
> same cadence as the other builders. Like for example pkg-desktop.f.o.
> People with desktops and laptops could point their pkg -r to that
> instead of huge things blocking someone who might want i dunno, asterix
> or other such ports usually used in a headless server environment.
> Most desktop stuff is leaf stuff.
> 
> I mean i get why these ports are blacklisted if the builders are building
> all possible ports in all possible combinations. Desktop is still niche.
> Then there's the question of the energy needed to build these things.
> Electricity is often the highest recurring cost for a server in a datacentre.
> I'd imaging the electricity bill being very high for builders.
> Maybe a way around that would be to on-prem where electric is cheaper,
> the actual builders which'd upload to whatever then goes on to distribute 
> the packages at the datacentre. That would be greener than everyone
> who needs these ports building them each individually.
> -- 

Hi.

It would be nice if chromium is brokend down into fine-grained
components and released per component (and build up for chrome
/ chromium / Iridium / ... / electron*) to minimize updates.

IIRC, this kind of thing was done for Xorg before.

But the significant difference is that Xorg was formerly
released as a large set of components, while chromium is
currently consists of single huge binary and its resources,
no individual libraries.

Now, at least lang/v8, which should be the Javascript engine
of chromium, is available as ports. So it wouldn't be mutually
impossible (maybe quite hard and beyonds me, though).

Regards.

-- 
Tomoaki AOKI    <[email protected]>

Reply via email to