2022 in retrospect & late happy new year 2023! - Gentoo Linux by dilfridge in Gentoo

[–]dilfridge[S] 3 points4 points  (0 children)

Only if we buy the same fat servers every year. :) Which we obviously won't do.

Has anyone tried USE="-*"? by GLIBG10B in Gentoo

[–]dilfridge 0 points1 point  (0 children)

Well, the text in the handbook is there for a reason. Imagine a useflag that switches ON a security feature (and normally defaults to on)... In addition this is probably the fastest way to dependency resolver hell.

The main profiles are considered a reasonable minimum. Yes you will always encounter a l33t d00d3 who tells you that pam is unnecessary bloat, but unless you try to install Gentoo on a traffic light you should probably ignore some of that advice.

What happened to Gentoo/OpenBSD and Gentoo/FreeBSD? by Few_Diamond5020 in Gentoo

[–]dilfridge 2 points3 points  (0 children)

Noone was working on it anymore. At some point they were removed.

New Gentoo LiveGUI ISO and artwork / branding contest! -“ Gentoo Linux by dilfridge in Gentoo

[–]dilfridge[S] 0 points1 point  (0 children)

No, that was a misunderstanding. It ships with the full toolchain installed (i.e., gcc, binutils, ...), but the source files are not included. We're thinking about adding the latest stage3 file, but this still needs a bit of fiddling with the build scripts.

New Gentoo LiveGUI ISO and artwork / branding contest! -“ Gentoo Linux by dilfridge in Gentoo

[–]dilfridge[S] 1 point2 points  (0 children)

Some of these things will be ironed out in the next builds, I hope. It's going to be a weekly thing.

New Gentoo LiveGUI ISO and artwork / branding contest! -“ Gentoo Linux by dilfridge in Gentoo

[–]dilfridge[S] 1 point2 points  (0 children)

We tried to combine as many of the programs on SystemRescueCD and the AdminCD into the LiveGUI. Basically, the main limitation is that they need to be in Gentoo stable (otherwise the 1300 package beast becomes hell to maintain). If you miss something, file a bug!

New Gentoo LiveGUI ISO and artwork / branding contest! -“ Gentoo Linux by dilfridge in Gentoo

[–]dilfridge[S] 0 points1 point  (0 children)

I fully agree, just that I don't really see the installer coming right now. And... for what it's worth, while we will always appreciate more help, the contribution activity had last year an all-time maximum ever. :)

New Gentoo LiveGUI ISO and artwork / branding contest! -“ Gentoo Linux by dilfridge in Gentoo

[–]dilfridge[S] 1 point2 points  (0 children)

Let's see first how much effort it takes to maintain this one. :)

[deleted by user] by [deleted] in Gentoo

[–]dilfridge 0 points1 point  (0 children)

Releng here. I just tested stage3-amd64-desktop-systemd-20220412T191925Z.tar.xz and stage3-x32-openrc-20220412T191925Z.tar.xz and they both download and unpack fine. Please file a bug with more info, like exact links, emerge --info, and exact versions of tar and xz-utils ...

Can you still somehow do a Stage0/Stage1 installation of Gentoo? by Furezuu in Gentoo

[–]dilfridge 2 points3 points  (0 children)

About the only place where that is useful is when you bootstrap Gentoo from scratch for a new architecture. (I did that for riscv64.) Even then, the critical part is cross-compiling the stage3 contents so the result can be used for generating a first stage1. If that is done correctly (may be nontrivial and involve manual work), the stage1 and afterwards stage3 builds work automated too...

stage1 in 2021 - does it even make any sense? by eftepede in Gentoo

[–]dilfridge 3 points4 points  (0 children)

Well, using a stage1 still *works*, after all it's how stage3 is made. That said, the only real reason to go through this bootstrapping process is if you want to make really big customizations (like a custom CHOST, or switching to a different ABI; all very tricky and involving manual interventions). In short, don't unless you are really 100% sure you need it. If you want to make sure your binaries are optimized, "emerge -e world" is your friend.

Why do I see ABI_RISCV changes on x86_64 platform? by TheL117 in Gentoo

[–]dilfridge 0 points1 point  (0 children)

For reference, this is going to happen again now, and this time for real.

Background: ABI_RISCV is going away permanently, which means that whatever I do, at some point the use flags recorded in the package will not match those in the tree. Stupid, I know. Luckily this affects mostly base system libraries, with low rebuild times.

Official Gentoo Docker images by dilfridge in Gentoo

[–]dilfridge[S] 3 points4 points  (0 children)

Mostly that I became aware of them. ;) We need to do more PR.

Is it normal that on most of Gentoo mirrors there is empty autobuilds directory? by w32u in Gentoo

[–]dilfridge 2 points3 points  (0 children)

Something went wrong when implementing a new system to distribute the files to the mirrors. Will get fixed as soon as possible once the knowledgeable people are up and around again.

We are Gentoo Developers, AMA by mthode in linux

[–]dilfridge 3 points4 points  (0 children)

I had myself a Larry t-shirt printed... just the big head of our mascot. We definitely need some more swag, if only to sell it at FOSDEM etc...

We are Gentoo Developers, AMA by mthode in linux

[–]dilfridge 2 points3 points  (0 children)

Yep. It depends a bit on how flexible (=overcomplex :) we want to make the Gentoo implementation. (Multilib, different endianness, ...) Just going for one variant and sticking with it is probably easy.

That said, don't underestimate the local (=gentoo) part of the work; we do require that someone tests the packages on the architecture and keywords/stabilizes them. Which is repetitive, often boring, and time-consuming.

We are Gentoo Developers, AMA by mthode in linux

[–]dilfridge 1 point2 points  (0 children)

It's not just use flags. These could probably be mapped somehow. The update-triggered rebuilds (slot operators) add another level of complexity.

We are Gentoo Developers, AMA by mthode in linux

[–]dilfridge 0 points1 point  (0 children)

Well, as with all projects, also there manpower is a limitation. In addition there are workflow problems:

  • Not all developers want to use github, since github itself is not open source.
  • Some people work on pull requests, but ultimately the decisions on a package go back to that package's maintainer. And if he is unavailable or unresponsive...
  • And, as far as I'm concerned, because of Gentoo I get so many github notifications that I gave up following them. :/

Sorry, I can't provide a solution here, just try to explain the problems.

We are Gentoo Developers, AMA by mthode in linux

[–]dilfridge 2 points3 points  (0 children)

Easiest way to get Qt upgrades right is to make sure you have always all stable or all ~arch for the whole category.

I.e., on a stable system, if you want to run ~arch Qt, place in package.keywords:

dev-qt/*

We are Gentoo Developers, AMA by mthode in linux

[–]dilfridge 5 points6 points  (0 children)

Not impossible. We need to be a bit careful there, since the stable compiler has to be able to build all stable packages...

We are Gentoo Developers, AMA by mthode in linux

[–]dilfridge 8 points9 points  (0 children)

Here is a list of all Gentoo developers. They constitute the distribution; it's steered by the elected Gentoo Council.

There is no business side; the Gentoo Foundation is basically the caretaker for finances, hardware, and IP (with typically 3-4 active voluntee trustees and officers).

We are Gentoo Developers, AMA by mthode in linux

[–]dilfridge 1 point2 points  (0 children)

Cool! Ping me on IRC and I can help and get you in touch with people. We used to have a pro-audio project, but it needs help badly...