Once installed, what do the EndeavourOS packages offer over bare Arch?

[freebird54]

Just for clarity - here they are:

EndeavourOS repo contents

┌05:33:56 WD= [~]
└───freebird@nest ─▶$ paclist endeavouros
akm 2.5.3-1
arc-x-icons-theme 2.1-3
downgrade 8.1.1-1
endeavouros-keyring 1-4
endeavouros-mirrorlist 3.1-1
endeavouros-theming 6.2-1
endeavouros-xfce4-terminal-colors 2-1
eos-bash-shared 1.2.14-1
eos-log-tool 1.4-1
eos-update-notifier 1.8.8-1
grub-tools 1.4.4-1
grub2-theme-endeavouros 20200919-1
inxi 3.1.07-1
mkinitcpio-openswap 0.1.0-3
paper-icon-theme 1.5.0-2
reflector-simple 1.4-1
welcome 3.4.36-1
yay 10.0.4-1

[Kresimir]

You’re missing a few. The complete list is:

Summary

akm
arc-x-icons-theme
downgrade
endeavouros-keyring
endeavouros-mirrorlist
endeavouros-theming
endeavouros-xfce4-terminal-colors
eos-base
eos-bash-shared
eos-hooks
eos-log-tool
eos-rankmirrors
eos-update-notifier
grub-tools
grub2-theme-endeavouros
inxi
keyserver-rank
mkinitcpio-openswap
nvidia-installer
nvidia-installer-db
nvidia-installer-dkms
pahis
paper-icon-theme
reflector-auto
reflector-simple
welcome
yay

The list was generated with

pacman -Sl endeavouros | cut -d' ' -f2

[freebird54]

I thought paclist would do better than that! No man entry though - so I guess it isn’t a surprise. I wonder what it is doing in there with its selections though! I just didn’t want to go to the git list for the quick post I was doing…

[Kresimir]

@freebird54

I wonder what it is doing in there with its selections though!

paclist endeavouros

shows you the packages you have installed on your machine, not the contents of the repos.

Exactly how it does it:

pacman -Sl "$@" | awk '/\[.*[[:alpha:]]+]$/ {print $2,$3}; /\[.*[[:digit:]]+]$/ {print $2,substr($NF, 1, length($NF) - 1)}'

[otherbarry]

@ideasman42

I can always check over the extra packages individually, too

pacman -Sl endeavouros

Will give you a list of Endeavour specific packages and which you have installed. There are not many (27?).

Some are theme related, some are maintenance ease of life, some are installation related (ie nvidia), a few are separately maintained AUR packages … bottom line is Endeavour is very close to Arch, and nothing like the bloated mess Manjaro has evolved into.

[Elloquin]

@otherbarry

nothing like the bloated mess Manjaro has evolved into.

Friendly reminder

@Bryanpwo

You can discuss other distros over here, as long as the discussion is civil and respectful to the other distro. We as EndeavourOS know how difficult it is to develop and maintain a distro. Therefore, we have and show respect to any distro and package developer out there and we don’t tolerate flamewars between distros over here.
A little tongue-in-cheek remark is allowed, but if you want to burn another distro down, we kindly ask you to do that somewhere else on the internet and not over here.

[fbodymechanic]

@Orca

reflector-auto, eos-welcome, a kernel manager and the eos-update-notifier

And. . . . This stellar community. What else could you need??

[Toni]

For me, it is not what EndeavourOS have after install that make me use it. But installing Arch without RTFM is.(Btw is my grammar correct?)

[Shjim]

what wrong with " Replace The Failure Mindset "

[freebird54]

Interestingly enough, Archway installs I have done lately seem to be picking up the endeavouros repo - I miss some of the goodies when I don’t have them! ( such as su_c_wrapper and checkupdatesext and sometimes Welcome for example) Sure I could live without them - but why?

[Alexander]

Have you tried installing Arch? That byitself is a barrier to entry for me. EnOS takes care of that and has an absolutely wonderful community.

[freebird54]

Think of it more as a hurdle - it seems deliberately to be set up to FORCE you read the wiki instructions carefully (including following links - even if you don’t yet know WHY they need to be followed) so as to prove you can find the trees no matter HOW dense the forest.

That said, I have done enough of them that I don’t really see the need to do more!

[ringo]

Would atleast encourage to try in vbox. It can atleast give some understanding but is always own choce to do also.

[keybreak]

I really love EndeavourOS hooks btw

[ideasman42]

@keybreak

I really love EndeavourOS hooks btw

What are they and when would you use them? (I tried searching online but couldn’t find a summary of this).

[kmartin]

This may help you.

Hooking

mkinitcpio - ArchWiki

[ideasman42]

@kmartin while I know the concept of hooks, I still don’t follow why I would care about them in the context of a linux-system. Is this only useful regarding mkinitcpio ? or are there hooks EndeavourOS has which I could make use of… and if so, what for?

[Kresimir]

One of the main things the pacman hooks in eos-hooks change is “Arch Linux” to “EndeavourOS Linux” in the /etc/lsb-release, /etc/os-release, and /etc/issue files. You can see exactly what it does here: https://github.com/endeavouros-team/PKGBUILDS/blob/master/eos-hooks/eos-hooks-runner

It’s an aesthetic change, which no impact to functionality. For example, this gives you EndeavourOS logo when you run neofetch.

EndeavourOS is pretty much just like bare Arch, most of the changes are superficial and aesthetic, and the few changes that impact functionality are intended to make it easier to use the OS, they are not very opinionated and, if you do not like them, you can easily remove them.

Personally, I think that’s a good thing, it’s one of the things that attracts me to EndeavourOS. If I wanted to use a more opinionated Arch-based distro, which offers much more over bare Arch, I’d probably use Garuda, which seems really nice. But I like a mostly bare Arch system I can configure to my liking, and I like the EndeavourOS community, so I use EndeavourOS.

[keybreak]

@ideasman42
What i mean is pacman hooks, for example one that tells you, that your update have packages which require reboot, ain’t that handy?

I mean sure i could check it manually or create my own…But it’s already there, that’s why i like it

[otherbarry]

@ideasman42

I still don’t follow why I would care about them in the context of a linux-system

To trigger an action automatically after the completion of a specific task.

For instance, the automatic re-generation of initrd and grub after a kernel update, using a pacman hook. Without a hook you would have to do this manually, failure to do so may lead to a non booting system, until chrooting in to correct.

There are others provided by EOS installation.

$ ll /etc/pacman.d/hooks
total 32
drwxr-xr-x 2 root root 4096 Nov 26 14:10 .
drwxr-xr-x 4 root root 4096 Nov  3 12:26 ..
-rw-r--r-- 1 root root  199 Nov  7 07:00 eos-hooks.hook
-rw-r--r-- 1 root root  634 Nov  7 07:00 eos-reboot-required.hook
-rw-r--r-- 1 root root  242 Nov 25 23:42 grub-fix-initrd-generation.hook
-rw-r--r-- 1 root root  373 Nov 25 23:42 grub-update-after-kernel.hook
-rw-r--r-- 1 root root  211 Nov  7 07:00 lsb-release.hook
-rw-r--r-- 1 root root  209 Nov  7 07:00 os-release.hook

The structure of a pacman hook is simple enough, any change to a target package will trigger the defined action.

$ cat /etc/pacman.d/hooks/grub-update-after-kernel.hook
[Trigger]
Operation = Install
Operation = Remove
Type = Package
Target = linux
Target = linux-lts
Target = linux-zen
Target = linux-hardened
Target = amd-ucode
Target = intel-ucode

[Action]
Description = Update grub after installing or removing a kernel or microcode.
When = PostTransaction
Depends = grub
Exec = /bin/sh -c "/usr/bin/grub-mkconfig -o /boot/grub/grub.cfg"

mkinitcpio hooks are … same same but different.