Adding endeavouros repo to vanilla arch

I’m trying to script the addition of the Endeavouros repo to vanilla Arch, and have the initial state working.

My question is about updates to the endeavouros-mirrorlist file that configures pacman.

How does my git repo detect an updated copy of the mirrorlist file and automatically update itself with the change.

I’m thinking that a pacman hook might be the best approach but don’t know that much about them. I see where the file doesn’t change that much, which is good, but it still needs to be accounted for in my script.

Thanks for reading.

Why doesn’t it just start with EnOS? The installer is capable of doing what’s effectively a basic Arch install (pacstrap base etc.) but with the EnOS stuff already included.

1 Like

The endeavouros-mirrorlist is a package like any other. So it updates itself when you update the system.
Is this what you mean?

AFAIK, all you do is add the EndeavourOS repo to the /etc/pacman.conf - and then pacman -S any of the pkgs you want from it. No tricks needed (and I have EnOS added to 2 Arch builds so far - I find I miss some of the goodies!)

I would suggest you have a look at the pkgs available, and try out the ones that might help you - this can include pacman hooks, theming stuff, and useful utilities like eos-pacdiff and eos-shifttime and RunInTerminal etc etc…

1 Like

I dont always have control of where other people start.

Why would they convert Arch to EnOS? What’s the point if they already have a working installation?

this is a script running on an EndeavorOS box that needs to update a git repo with the updated mirrorlist file. I think pacman hooks for that package is the right way to address the issue, at the very least copy the mirrorlist.pacnew file to the repo and I can commit it when I get there.

I think you’ve missed the point. Maybe thats my fault. I’m working on a set of scripts for a project. The project is intended to be OS agnostic to the extent possible, so when some packages need to be installed, they may be from the arch aur, or they may be from a deb/ubuntu ppa. The arch branch of the project will check for yay and try to install it if required, but this is just easier if the arch box subscribes to the ENOS repo. I could script a manual install of yay with git, but this seemed like it was easier.

Yes, given there was zero context in the OP. :stuck_out_tongue_winking_eye:

That would very likely upset a number of Arch users - you’d be adding the EnOS keyring to an Arch system and thereby providing root access.

There must be a better approach to this. If this is for a single piece of software that you’re trying to distribute via various channels then running an unofficial user repository would be better, then Arch users can add it if they want to.


So you have a program that has an install script and in order to install dependencies for that program, you want to convert the user’s vanilla Arch system into EndeavourOS. Am I understanding this right?

If so, that’s… well, utterly insane.


Ya,I don’t get it either.

Who goes thru the effort of installing Arch. . . To then need help adding a repo afterwards?

It’s gotta be a very small percentage of users this applies to.

1 Like

funny how life works, but i was musing today about the same - not because i have any intention of doing it but just a case of how could it be done, anyway, this popped up from last year and might add a little colour to the thinking! Adding Endeavour os repo on Arch Linux

1 Like