How do you quote somebody who has used “[sic]” incorrectly?
Uncategorized
1
Posts
1
Posters
1
Views
-
How do you quote somebody who has used “[sic]” incorrectly?
-
undefined evan@cosocial.ca shared this topic
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@mos_8502 oh and another more modern choice you could make too, depending on application: disregard package management entirely and treat the entire OS as an immutable image that's built as an atomic unit, with updates being done by having a pair of A/B partitions. You boot off the current active partition, and to update the OS you write out the entire new image to the inactive and reboot onto it.
The Fedora Atomic distros do this, as do the Universal Blue ecosystem (they're essentially running the "new" atomic stack that future Fedora will use). CoreOS was arguably the OG at this for widely known distros, although this is how a large swatch of embedded linux operates, using either buildroot to generate images or Yocto (whose build system is a horrific crime, but it's also very powerful, can generate whole disk images _and also_ a stream of delta updates for efficient upgrading, and is widely supported by embedded linux hardware and software vendors so a lot of stuff ends up using it, even though I find it horrible every time I try touching it)
-
@mos_8502 if you're Ubuntu, you just start with Debian, and then make it worse.
That's also how I do it for the OS my employer ships on our robots. I start with Ubuntu and mostly make it worse, but also make it better by replacing snap packages with regular debs.
-
@mos_8502 The biggest pains, if you're not reusing someone else's package manager: how do you express dependencies between packages? Can you have optional deps like debian's "recommended" ? Can you have virtual packages that can be provided by multiple concrete packages (I don't have an example on tap but debian, arch, gentoo all support this for stuff like swapping out libc implementations or pulseaudio vs. pipewire), how do you version packages where the upstream might have an unhelpful or missing versioning scheme of its own, how do you handle the million different build systems that upstream uses, how fancy is your dependency resolution algorithm (can be anything from "unhelpfully useless" to "NP-hard and sometimes takes hours to compute a solution" - most useful distros land somewhere in the middle).
None of this _has_ to be hard, at every step you can make some simplifying assumptions/decisions that cut off some flexibility from your distro in exchange for a simpler system to build/use/maintain. There not being any "correct" answer is why there's a million distros with more showing up all the time.
-
Eh sì: sembra che eolico, solare, idroelettrico siano più convenienti 🤷♂️. Le rinnovabili rischiano di far saltare i conti del nucleare francese - Startmag https://www.startmag.it/energia/edf-rinnovabili-costi-manutenzione-centrali-nucleari/
-
Yes.
Then you may want to include software A that needs libB<1.5 and software C that needs libB >1.5.if the distro intends to ship software like Python with its own random and self-conflicting ideas about version management, things start to get hairy.
The solution-du-jour seems to be a modernized version of "build a giant tarball with A and its dependencies and call it a day" (then call it snap , flatpack or whatever).
-
@mos_8502 you hit it right on the nose
-
@mos_8502 Pretty much. And along the way make a million policy decisions for what you want your distro to be. What libc options does it use, what filesystem layout, what default kernel config, which packages with which options, does your package manager support easily recompiling with different flags, etc.
I'm told Gentoo is a good example at one end of the spectrum, a source-based distro (where technically every install involves building from source with the exact bespoke flags and configs you desire, although these days there's a binary cache for the "common" build options). At the other end of the spectrum is probably debian and fedora, very binary-oriented distros where building packages and installing them are two very different sets of operations.
Oh and you'll also need to make yourself an installer for your distro once you have a package set, although these days I'm told you can do that pretty easily by slightly customizing the Calamares installer.
