I expect that'll be a recurring experience, hence the "word by fucking word" sura.

You're the coherent entry point, that's what you do, own it as such.

Thank you, Sir. The coherent entry point I must be then.

I re-read La Serenissima and Personal Sovereignty this morning and the identity being allodial property of the person point sunk in :

La Serenissima does not recognise nor will ever enforce any sort of claim of any entity that purports to impinge on the sovereignty of persons. No entity may claim rights to person's identity under this rule, and if they try to they're being the enemy and should be treated like the enemy. For all intents and purposes identity is allodial property of the person therein represented, and no convention may touch it.

And layering on the factor of the leverage of invested individuals the advantages amplify.

If project C has a decision making system formed out of 18 elements, which each obviously will require a separate pitch, as well as 39 groups formed out of the 18 elements in varying compositions, while project D has a decision making system formed out of one single person, we can say that D offers leverage and couldn't be bothered to mention C again.

On GCC :

Amusingly, I mostly use 4.4.7.

Do you think it's worth putting on the table for analysis next to 4.7.4 and 4.9 ?

Sure, why not.

Ok, GCCs 4.4.7., 4.7.4 and 4.9.4 are all up for consideration.

You're the coherent entry point, that's what you do, own it as such.

> Do you think it's worth putting on the table for analysis next to 4.7.4 and 4.9 ?

Sure, why not.

> I interpret Eulora being an implicit client means new hardware shall be supported, so EFI

I dunno Eulora cares about this either way ; your problems will start once various systems won't boot your stick because uefi considerations, for instance.

> in which case what, every GUI app ships its own GTK or Qt?

No, every GUI app is a patchset on the GTK tree.

> OK, then what? You still need to build it.

Hence why only-one-build-system, so it's ~implicitly~ clear "then what". This was one of those implcits that never needed explicitation, it should have forever stayed implicit.

What does a Busybox + Gnu Coreutils approach look like in comparison ?

You can certainly use busybox or whatever lightweight things by default with GNU stuff as an option.

Thinking aloud re portage and similar vs. V, as I see it either a common standard, or tool to abstract over a proliferation of standards, is needed for how applications get built and installed. V gives you a source tree in a location of your choice. OK, then what? You still need to build it. There might be dependencies - unless we're banning those outside of the base, in which case what, every GUI app ships its own GTK or Qt? Every script ships own interpreter? Then how does the rest of the system find it, e.g. installing to somewhere in the shell search path.

In the domain breakdown, note that firmware and bootloaders are a pretty different domain from init scripts and syslog; more in common with the kernel really.

Re LILO, I'm not too thrilled with the code from having poked at it. I'd readily believe GRUB is worse, though perhaps there's a distinction to be made between grub 2 and legacy. Concur re UEFI being evil but necessary if modern hardware is relevant. GRUB isn't strictly necessary to work with it, e.g. there's the in-kernel stub loader, and there's some ELILO thing. One particular pain is it's far more complex than BIOS and vendors don't always implement it consistently.

Re GNAT - it's Adacore GNAT that's in use, right? So it's at least somewhat divergent from the GNU 4.9 tree; I don't know if this is just in the frontend (written in Ada) or the backend (C/C++ and machine definitions) too. Probably worth researching, e.g. better to be able to fix backend bugs in one place if possible.

So he got to build X11 statically? That'd be great news, in any case, it's something worth writing about.

Sadly no, this was on a dynamic musl system. I haven't tried it static yet; expecting a mess due to the dlopen'ed module design.

I didn't mean to imply that C++ was going away anytime soon -- and in point #2 there noted it as a front-end -- just that 4.7.4 doesn't require C++ for the minimal build of the compiler itself.

This; and incidentally I suspect it accounts for a large part of the difference between my ~1 hour, ~3G temp space bootstrap process and the apparently >10G for cuntoo. Also, AFAIK it's not that they totally rewrote the codebase in C++ or anything, but started to compile in C++ mode and make changes assuming it.