🦎 dotfiles-openSUSE

The openSUSE OS-native layer — zypper, Tumbleweed + Leap, over the shared Core.
Explore the docs »

View Demo · Report Bug · Request Feature

Table of Contents

1. About The Project
   • Languages
   • Tools
2. Getting Started
3. What's In This Layer
4. Contributing
5. License
6. Contact

About The Project

dotfiles-openSUSE is the OS-native layer for openSUSE (Tumbleweed + Leap) — one node in a cross-platform dotfiles system. The shared Core (zsh, tmux, Neovim, git, starship, mise) is authored once in dotfiles-core and vendored under core/ via git subtree, so a clone is self-contained. This repo adds only what is genuinely openSUSE: zypper, Packman, AppArmor, Btrfs/snapper, and the Wayland clipboard shim.

openSUSE is stamped from the dotfiles-Fedora template per the porting matrix. The full docs live on the documentation site.

The system is three layers, each building on the one below:

Layer	Lives in	Owns
Core	dotfiles-core → vendored into every OS repo's core/	zsh, tmux, nvim, git, starship — identical everywhere
OS-native	dotfiles-{MacBook,Windows,Fedora,Arch,openSUSE,Alpine,Gentoo} (this repo among them)	package manager, clipboard, paths
Role	dotfiles-Kali, dotfiles-Defense	offensive / defensive tooling

Languages

No new languages — this layer is shell and package config over Core's language stack.

Tools

• 
• 
• 
• 

(back to top)

Getting Started

Prerequisites

An openSUSE box (Tumbleweed or Leap, desktop or a WSL image) and Git. Everything else — zsh, tmux, nvim, starship, and the modern-CLI stack — is provisioned by bootstrap.sh.

Installation

git clone https://github.com/dotgibson/dotfiles-openSUSE ~/dotfiles-openSUSE
cd ~/dotfiles-openSUSE
./bootstrap.sh
exec zsh

core/ is a vendored subtree and is already present in a clone — there is no submodule step. bootstrap.sh is idempotent: it refreshes zypper metadata, installs the package list, and symlinks Core + the openSUSE layer into place. It only refreshes metadata — the dup-vs-up upgrade choice stays yours. Flags: --links-only (re-link without touching zypper), --no-flatpak.

(back to top)

What's In This Layer

Only what changes with the OS. The heavy lifting — the shell modules, editor, and prompt — comes from vendored Core; this repo owns the openSUSE specifics:

• bootstrap.sh — zypper provision + Core/OS symlink wiring (idempotent)
• install/packages.txt — the zypper package list (modern CLI stack)
• os/opensuse.zsh — clipboard + package-manager aliases → ~/.config/zsh/os.zsh
• core/ — vendored from dotfiles-core (read-only here; edit upstream)

The things that actually bite on openSUSE — the Tumbleweed dup vs Leap up split, the excellent solver, AppArmor (not SELinux), Btrfs/snapper rollback, and the Packman codec repo — are written up on the hub, alongside the per-distro porting matrix:

→ dotfiles-openSUSE on the documentation hub

(back to top)

Contributing

This is an OS-native layer, so the contribution rule is a boundary rule:

1. Never hand-edit core/. It is a vendored copy of dotfiles-core and is overwritten on the next sync. Fix shared config upstream in dotfiles-core, run make audit there, then make sync fans it out here.
2. Keep changes genuinely openSUSE. If it would be identical on every distro, it belongs in Core; if it changes with the operator, it belongs in a role repo.
3. Green the lint gate. This repo's CI runs shellcheck + bash -n / zsh -n on the repo-owned shell (the vendored core/ is excluded — it is gated upstream).

Bugs and ideas: open an issue.

(back to top)

License

Distributed under the MIT License. See LICENSE for more information.

(back to top)

Contact

Garrett Allen - @gerrrrt - garrettallen2@gmail.com - LinkedIn

Project Link: dotgibson

(back to top)