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…
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.
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?
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!
@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?
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.
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"
but is always own choce to do also.
