this post was submitted on 05 Feb 2024
68 points (100.0% liked)

Linux

48310 readers
645 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

It was announced late last year that Gentoo is now offering binary versions of their packages. I’ve always had an interest in Gentoo, but the need to compile everything has always turned me away from it. I run Arch because it gives me the sense that I have more control of my system, when compared to other distros like Ubuntu, for example, but it still keeps things simple enough for day-to-day use. That being said, when compared to Gentoo, Arch is still rather restrictive, so if there exists an alternative that offers Arch’s simplicity, and also the potential for customization of Gentoo, then I would gladly switch. I am wondering if Gentoo’s new binary offerings fit this description. From what I understand, it removes the need to set use flags, and to compile any packages, but it still allows you to maintain full control over your system.

So, in summary, is a binary Gentoo functionally equivelant to Arch Linux, but with more control over the system? I would like to know more about the following:

  1. Does the OS installation change, and, if so, how?
  2. Does package installation, updates, and maintenance change, and, if so, how?
  3. Do system updates change, and, if so, how?
  4. Do you lose any potential control over the system when using the binaries, rather than compiling from source, and, if so, what?
  5. Are there any differences in system stability? Can I expect things to break more readily on a binary Gentoo compared to Arch Linux?

Just a disclaimer: I have never used Gentoo -- all my knowledge is second hand, or from skimming documentation out of curiosity. Please correct any inacuracies that I may have in my knowledge.

you are viewing a single comment's thread
view the rest of the comments
[–] Kangie@lemmy.srcfiles.zip 8 points 9 months ago (2 children)

This has been answered a bit already but:

So, in summary, is a binary Gentoo functionally equivelant to Arch Linux, but with more control over the system?

Perhaps, if that's how you view the world. I'd argue that it's better as I've never seen Gentoo ship a version of curl that broke Portage...

I would like to know more about the following:

  1. Does the OS installation change, and, if so, how?

You basically unpack a tarball, select a kernel, install a bootloader, and go. It's no different to before except that you can optionally choose to enable the use of binary packages.

  1. Does package installation, updates, and maintenance change, and, if so, how?

If comparing to arch, you use portage to handle that but the concept is the same.

Gentoo has a great system for managing configuration changes when a package updates a file that you've customised.

  1. Do system updates change, and, if so, how?

This question doesn't make much sense to me. What is a "system update"? Isn't that just updating all of your packages at once?

  1. Do you lose any potential control over the system when using the binaries, rather than compiling from source, and, if so, what?

Yes and no. If you customise your USE flags the binary won't be suitable and instead portage will build the package as you requested it

  1. Are there any differences in system stability? Can I expect things to break more readily on a binary Gentoo compared to Arch Linux?

Hahahahaha. Hahahahahaha. Hahaha. Ha.

Arch is notorious for shipping barely tested software to have the higher version number in their repo.

Gentoo enables users to select the stable or testing path, on a per package basis, so you have to opt into packages that haven't been well tested and even those are typically better tested than arch.

[–] WalrusByte@lemmy.world 2 points 9 months ago

This question doesn't make much sense to me. What is a "system update"? Isn't that just updating all of your packages at once?

I would think syncing the repos and emerging the @world set would be considered a system update. But I guess that is a bit different from how most distros do it.

[–] Kalcifer@sh.itjust.works 2 points 9 months ago (2 children)

I’ve never seen Gentoo ship a version of curl that broke Portage…

Aha, would you mind elaborating? That sounds like quite the issue for Pacman to break its own dependencies.

You basically unpack a tarball, select a kernel, install a bootloader, and go. It’s no different to before except that you can optionally choose to enable the use of binary packages.

Ah okay, I was under the impression that the installation didn't require installing from source with the new binary system -- I thought it was more akin to Arch's installation where you just select your kernel binary in Pacman, then download, and install.

Gentoo has a great system for managing configuration changes when a package updates a file that you’ve customised.

Would you have any resources/documentation for me to look into this more?

This question doesn’t make much sense to me. What is a “system update”? Isn’t that just updating all of your packages at once?

I misworded my original post -- I was referring to things like updating the kernel. I thought that maybe the kernel would be a binary, so it would not have to be recompiled like how I would assume it usually does.

Gentoo enables users to select the stable or testing path, on a per package basis, so you have to opt into packages that haven’t been well tested and even those are typically better tested than arch.

This sounds very appealing to me, but I must admit that these sorts of configurations do seem like they would be mildly daunting to juggle on a production machine.

[–] Kangie@lemmy.srcfiles.zip 2 points 9 months ago (1 children)

Aha, would you mind elaborating? That sounds like quite the issue for Pacman to break its own dependencies.

There was a bug with http/2 in a particular version of curl, which was very quickly updated in the arch repos and rolled out to users; It broke pacman's ability to sync.

It's one of those frustrating things that happens, and someone has to hit the bug first. It's nice to have a "stable" and "testing" branch so that users explicitly opt-in to bleeding edge packages.

Ah okay, I was under the impression that the installation didn't require installing from source with the new binary system -- I thought it was more akin to Arch's installation where you just select your kernel binary in Pacman, then download, and install.

This is just the base system - it's like any other distribution's base install except that we don't have an official 'installer'; Gentoo distributes tarballs that users unpack following the guidance in the handbook.

From there most packages can be installed as a binary if the USE flags line up (and it has been asked to do so), otherwise portage will compile it for you.

After unpacking the system image you can install a binary kernel, have portage compile one for you, or manage it manually (but still let portage fetch sources)

Gentoo has a great system for managing configuration changes when a package updates a file that you’ve customised.

Would you have any resources/documentation for me to look into this more?

https://wiki.gentoo.org/wiki/Dispatch-conf

I misworded my original post -- I was referring to things like updating the kernel. I thought that maybe the kernel would be a binary, so it would not have to be recompiled like how I would assume it usually does.

It comes down to user choice. That can now be entirely binary or from source (or from source but managed by portage)

This sounds very appealing to me, but I must admit that these sorts of configurations do seem like they would be mildly daunting to juggle on a production machine.

It's actually pretty straightforward - you nominate packages that you want to run on ~arch (testing) and add them to some config files. Portage handles the rest.

[–] Kalcifer@sh.itjust.works 1 points 9 months ago (1 children)

This is just the base system - it’s like any other distribution’s base install except that we don’t have an official ‘installer’; Gentoo distributes tarballs that users unpack following the guidance in the handbook.

[...]

After unpacking the system image you can install a binary kernel, have portage compile one for you, or manage it manually (but still let portage fetch sources)

It may be best for me to simply attempt to install Gentoo in a VM to see for myself, but, out of curiosity, how does the base image differ from something like the .iso that Arch Linux distributes to allow you to install the distro? So, if one were to install a binary kernel, would they still need to initially compile anything? Or could one theoretically do a full Gentoo install without the need of compiling?

[–] Kangie@lemmy.srcfiles.zip 1 points 9 months ago

No idea, I don't arch.

Theoretically you can install a desktop amd64 system using the binhost without compiling anything (or if compilation is required there won't be much), I haven't tried though I have seen other users do it successfully.

[–] bubstance@lemmy.ml 1 points 9 months ago* (last edited 9 months ago)

I thought that maybe the kernel would be a binary, so it would not have to be recompiled like how I would assume it usually does.

There are options for binary kernels, just so you are aware.

As for documentation related to configuration of portage and /etc/portage/make.conf, I would, of course, be remiss to not point you to the Gentoo Handbook. The wiki contributors do really great work and the community is generally quite welcoming and open to implementation-specific questions.