Not sure whether you duplicated the line by mistake or if there's a legitimate reason why the operation is run twice?

Whenever I run the setup command I get a syntax error;

./setup: 137: Syntax error: "}" unexpected

As I was testing the packages install feature, I noticed that this function was run although I already had paru^AUR installed:

What about using something like this instead, so that paru^AUR is cloned and installed only if it's not already installed?

if [[ "$packagemanager_main"  = 'Pacman' ]]; then
    if ! command -v "paru" >/dev/null; then
        packagemanager_list="$packagemanager_list AUR"
    fi
        packagemanager_list="$packagemanager_list Flatpak"
fi

Just for your information:
https://github.com/ssh0/dot

Current state:

#TODO

• Linux:
  • Portage (for Gentoo)
  • Zypper (for OpenSUSE)
  • Slackpkg (for Slackware)
  • SBO (for Slackware)
  • APK (for Alpine)
  • EOPKG (for Solus)
  • Nix (for NixOS)
  • DNF
  • YUM
  • Urpmi
• BSD:
  • OpenBSD PKG (for OpenBSD)
  • PKG NG (for FreeBSD and DragonFly)
  • Mports (for MidnightBSD)
  • PKG IN (for NetBSD)
• MacOS:
  • MacPorts
  • MAS
• Other:
  • Termux PKG (for Termux)
• Language:
  • Basher (issue)
  • BPKG (issue)
  • Node.js
    • Yarn
    • NPM
  • PIP
    • PIPX

You can help us by summit:

• A mark (3 letter)
• A package manager tool
• A full command with flags to install packages
• A setup function
• NOTE:
  • The less user input needed the better, you should add no-confirm flag like --noconfirm, --non-interactive, --assume-yes, ... to the commands
  • For more Clarity, use full flag instead of short flag (E.g: use --sync over -S)

Example:

Pacman_MARK='PAC'

Pacman_PM='pacman'

Pacman_COMMAND="$PERMISSION_COMMAND $Pacman_PM --sync --noconfirm --needed"

superbbootstrap_Pacman() {
	sudo pacman --sync --sysupgrade --refresh --noconfirm --needed
}

NOTE: $PERMISSION_COMMAND is default to sudo on Linux and doas on BSD

I had this error until I changed Pacman update command to always answer 'yes' instead of 'default option' (see #15):

When the upstream setup file changes, integrating those changes can be complicated if you have custom steps. It would be nice to split the file in 2 parts, one functional and one for configuration, and maybe create a helper function for symlink_*.

./setup.sh:

Install packages

Before symlink step

Symlink to home (/home/username)
./setup.sh: line 200: superbbootstrap_batch_symlink: command not found

Symlink to root (/)
[sudo] password for username:
sudo: superbbootstrap_batch_symlink: command not found

After symlink step

I presume there is something wrong with this block?

Hi! I'm trying to bootstrap a VM from my laptop. Both run Hash Linux - Arch-based distro.
My packagelist looks like this (I use only PAC: and AUR: suffixes):

setup is unchanged.

When I clone the repo to VM and run ./setup, it makes symlinks but doesn't install any packages. The output is this:

Maybe I'm not doing something correctly, but this morning I migrated my dotfiles over to this and when I try to run the setup I get the output "Install packages" but nothing further, it just jumps to the symlinking. my packagesllist can be found here https://gitlab.com/obyx/dotfiles/-/blob/master/packageslist

Hi everyone!
Turned out this line will not work in recent versions of Ubuntu (and maybe many other distros), because their system's Python doesn't have the ensurepip module. Ubuntu users are forced to install pip by this command: sudo apt-get install python3-pip.

The possible solution is to use this script whenever Python says "No module named ensurepip". But it may interfere with the way PIP is meant to be installed by the developers of a particular distro.

What do you say to that?