Can I input an app list to install during an eos install?

What I mean is installing apps I have in my current version during a new eos install.

Yes. https://discovery.endeavouros.com/installation/customizing-the-endeavouros-install-process/

2 Likes

To get list of packages installed, you can use pacman.

  • List all explicitly installed native packages (i.e. present in the sync database) that are not direct or optional dependencies: pacman -Qent

(lifted from Arch Wiki)

You can pipe the output to cut -f 1 -d " " for removing version suffix and listing only package names.

Installing on new system is done as manuel linked above.

1 Like

I do not find user_pkglist.txt anywhere. Could this be another non newbie friendly tutorial? Am I supposed to boot up the iso, and look for the file then?

This is how I understand the tutorial from looking at the images

This is from the beginning of the linked article:

EndeavourOS provides users a couple of ways to customize what to install.

User Packagelist

File /home/liveuser/user_pkglist.txt

This is the easy way to add your favorite package names to be installed. Simply open the file with the texteditor and add packages to the file, before starting the installer!

So you boot up the installer, there you can see the file already. It has some comments in it. You just add your package names into that file, one per line.

Note that you should restart the installer window:

  • close the existing installer window (Welcome)
  • restart Welcome, for example with command: eos-welcome
1 Like

Another way to do this is to just add a “q” on there.

pacman -Qentq

That’s right, this file is in the live environment.

An easy way to add your packages to this file is to use an online pastebin. For example, on your old installation you can grab the package list and pipe it to eos-sendlog.

pacman -Qentq | eos-sendlog

The command will output a URL. Be sure to write it down, or take a picture or something if you need to.

From the live environment (on the new system, before you run the installer), you can open up a terminal and curl down the list you made and attach it to user_pkglist.txt.

curl https://[whatever the URL is] >> ~/user_pkglist.txt

Then, run the installer like normal and enjoy having all your normal packages when it is finished.

1 Like

The discover.endeavouros link above mentions limitations.

Limitations for the commands

The commands are run as the root user, so

  • AUR packages cannot be installed
  • some commands do not run properly as root
  • files modified under $HOME need to be chown‘ed from root to the real user

Just to clarify, that doesn t have anything to do with packagelist.txt? I have several apps from AUR that I want to add to the list.

It also states:

In addition, commands written into this file must never stop e.g. for asking any confirmation. So, for example, pacman must be used with option --noconfirm to prevent stopping.

Does this have to do with using the packagelist.txt feature?

The installer can’t install AUR packages. Only repo packages. You will need to install the AUR packages after the install is complete.

No

1 Like

OK. So does

pacman -Qent

differentiate between AUR and repo packages?
Also, There is mention above, of removing package version numbers. Are version numbers needed/required in packagelist.txt? And I assume the latest version would be installed if no version number is needed/included. Correct?

This doesn’t list AUR stuff

No, you assume correctly

1 Like

Pacman has no idea where a package came from. pacman -Qqm lists packages not currently available in the repos.

No, they should be names only.

You can’t include version numbers and the latest version will always be installed.

1 Like

pacman -Qqem > ~/packages-AUR.txt
is what I use to back up the list of my non-repo packages
to reinstall you can use something like:

yay -Syu --needed - < ~/packages-AUR.txt

3 Likes

Concerning using, “something like”, your command; that implies a knowledge of coding that I do not possess though I do see that you are having yay use pacman arguments which is baffling to me…

yay calls pacman for most operations so you can use any pacman options with yay.

Good to know. I can only select one solution, but you all helped me understand it. Thanks. :partying_face:

Implies indeed to mark that you have to know what it is doing… mainly because you may use a different naming for the packages list file or another path.
And there is ~/ in use, this could not work in cases.

still good to do that, as it helps keeping forum clean posts will close when a solution is selected.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.