Possibly add -y to pacman command [config.sh]

[mrgreen3]

Pacman -S will of course install a package but adding 'y' will update repos, just in case there is an update available.

Depending on how script is run you may not need to add sudo to commands.

As this is more for you own use I would suggest repo goes private, until you wish to share.

Still do not see the need for .sh as config.sh does not even look like a script.

Rest is well laid out and comments are useful.

[Imdabossou]

I am doing all of my pacman package installs during the install.json that runs with archinstall, so I think these should pull in the latest version. The config part remaining should just be AUR packages, and I believe yay should build the latest here.

The "script" currently just pulls the text line by line and feeds it into a terminal, so unfortunately each line does require sudo if it needs elevated permissions.
My thought behind the .sh was if I am piping it into a bash terminal, it may be more inclined to execute text coming in from a .sh extension. I'm not actually sure if it is required whatsoever as I haven't tested it. As it worked I have just left it how it is.

I am loading in the files here over the internet from a booted Arch install ISO, so while this is for my own use, the repo does need to be public for the files to be reached during the installer. Because of this I will not put any files here that have personal information or credentials. This is why I have not included the user credentials section of the archinstall json file, so the Root password & User account fields are required to be completed manually.

Of course the Disk configuration section is going to be specific to my set up too, so if this json is being imported on another machine, I would recommend Disk configuration is redone as well. These are the settings I used.

Use a best-effort default partition layout
(select disk)
btrfs
Yes (use BTRFS subvolumes with a default structure)
Use compression

I will show the process below.

Loading config in

json loaded

After install it will ask if you want to chroot into new install. I originally planned for the config to happen inside the chroot, but some commands just don't work when ran this way, I'm not sure why. Do not use the chroot and reboot into the new installation.

Run config from console

Completed

[mrgreen3]

`
class BangProfile(XorgProfile):
def init(self) -> None:
super().init(
'Bang',
ProfileType.WindowMgr,
description=''
)

	self.custom_settings = {'seat_access': None}

@property
def packages(self) -> List[str]:
	additional = []
	if seat := self.custom_settings.get('seat_access', None):
		additional = [seat]

	return [
		"sway",
		"swaybg",
		"swaylock",
		"swayidle",
		"sway-contrib",
		"waybar",
		"otf-font-awesome",
		"rofi-wayland",
		"brightnessctl",
		"pavucontrol",
		"foot",
		"xorg-xwayland",
		"git"
	] + additional

@property
def services(self) -> List[str]:

`

I changed name of profile so not to conflict with sway.py [Bang!] Added packages I wanted.

[mrgreen3]

Json file simply pulls in a git repo of my configs! It does not work at the moment as I was trying to clone into a non empty folder. Easy fix!

You could of course add needed packages to json file but sway.py file includes lightdm by default! Which seems a little dumb as SDDM is far better. Not sure why it would be default....

You can of course still add packages during install or even via chroot and make changes...

[mrgreen3]

For simplicity I think running with a json file would be the way to go. User would then only have to select given desktop. If you change sway.py then user still has to select a desktop...

I could and might even make an archinstall wrapper to run my json file from the start.

Many ways to achieve the same goal.... Thinking now if archsintall runs json file before install menu? Now there is a thought.