1---
2title: Arch Spin pt. 3 - packages.x86_64
3description: Getting all the packages you currently have installed from the Arch repos installed to your Arch ISO
4author: Amolith
5cover: /assets/pngs/arch-spin/pt-3.png
6date: 2018-08-18T16:52:42-04:00
7draft: false
8categories:
9 - Technology
10tags:
11 - Arch Linux
12 - Arch Spin
13---
14
15## Package configuration
16As I said in the last post, this is the file in which you list the
17applications you wish to install. I won't list the defaults because
18there a lot. *However*, this basic setup only builds to a total of ~440
19MB so you can add *many* more applications.
20
21I want the setup on this bootable to be exactly the same as what I
22currently have on my system. I did not want to manually enter every
23single package though. Thankfully, pacman is a feature-complete tool and
24it lets you get a *lot* of information about installed packages. `pacman
25-Qne` lists all the currently installed packages that you explicitly
26installed. It does not list dependencies of those applications. What I
27did was run `pacman -Qne >> ~/liveiso/packages.x86_64` to add all the
28apps I have installed from the official Arch repos to the end of the
29file so nothing was overwritten.
30
31After, I ran `pacman -Qni >> official.txt` so I could get information
32about all those packages and decide whether or not I wanted to keep
33them. For example, I removed some stuff from deepin that I no longer
34used, SuperTuxKart, and a lot of other stuff. This shrunk my iso from
353.6 GB to 2.5. Now I have a lot of space to use for installing my
36applications from the AUR. This includes [making a custom
37repo](https://wiki.archlinux.org/index.php/Pacman/Tips_and_tricks#Custom_local_repository)
38for the packages and [building them in a
39chroot](https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot)
40so you make *sure* you have all the needed dependencies while keeping
41your system from being messed up while building.
42
43All of this will be discussed in the next blog post (when I get to it).