extern/nix-config
1
0
Fork 1
mirror of https://github.com/donovanglover/nix-config.git synced 2025-02-02 02:49:44 +01:00
Code Issues Packages Projects Releases Wiki Activity
53f3ef09f4
nix-config/.archlinux/PKGBUILDs/tari-core/PKGBUILD

65 lines
1.1 KiB
Bash
Raw Normal View History

meta: Add PKGBUILDs Instead of having one big PKGBUILD, I have opted instead to split my Arch configuration into multiple PKGBUILDs. Of course, splitting the packages *too much* has diminishing returns, but some separation makes it easier for both myself and others to pick and choose any wanted functionality.
2018-11-13 02:59:39 +01:00
pkgname=tari-core
PKGBUILDs: Merge tari-dev with tari-core Not all of these packages may be useful to everyone, and that's fine. Any list I create won't satisfy everyone, but reducing the number of PKGBUILDs makes it easier to see and change all the packages installed on the system as a whole. Due to the nature of how Arch Linux works, most users won't even need my PKGBUILDs. With the exception of setting up X with a bare-minimum window manager, installing and configuring most software is as simple as using pacman to install that software and symlinking any config files you want to their relevant directories, if any.
2018-12-07 23:47:43 +01:00
pkgver=0.4.0
PKGBUILDs: Merge tari-cli with tari-core Realistically, if I'm installing the tari packages, I more often than not want everything with it. If I am aiming for a minimalist setup without X11 or Wayland, I will probably not use the tari packages anyway.
2018-12-07 22:11:11 +01:00
pkgrel=1
pkgdesc="My Arch Linux setup"
meta: Add PKGBUILDs Instead of having one big PKGBUILD, I have opted instead to split my Arch configuration into multiple PKGBUILDs. Of course, splitting the packages *too much* has diminishing returns, but some separation makes it easier for both myself and others to pick and choose any wanted functionality.
2018-11-13 02:59:39 +01:00
arch=('any')
PKGBUILDs: Add tari-desktop, tari-cli, and tari-bspwm Now that I understand more about how GNU/Linux distributions, display managers, and X sessions work, it makes sense to separate meta packages based on environment used. When you use a display manager, you're just starting X in a fancy way. Since you can run any program you want on the X server, it is easy to install multiple desktop environments on the same machine and switch between them easily, provided your setup is adequately modular (which it should be by default).
2018-11-25 19:01:44 +01:00
depends=(stow
python-pywal
rng-tools
fd
exa
ripgrep
fzf
jq
zip
unzip
p7zip
unrar
borg
openssh
PKGBUILDs: Merge tari-cli with tari-core Realistically, if I'm installing the tari packages, I more often than not want everything with it. If I am aiming for a minimalist setup without X11 or Wayland, I will probably not use the tari packages anyway.
2018-12-07 22:11:11 +01:00
openvpn
mpd
mpc
ncmpcpp
htop
neofetch
fdupes
youtube-dl
ranger
weechat
ncdu
task
cmatrix
imagemagick
lolcat
PKGBUILDs: Merge tari-dev with tari-core Not all of these packages may be useful to everyone, and that's fine. Any list I create won't satisfy everyone, but reducing the number of PKGBUILDs makes it easier to see and change all the packages installed on the system as a whole. Due to the nature of how Arch Linux works, most users won't even need my PKGBUILDs. With the exception of setting up X with a bare-minimum window manager, installing and configuring most software is as simple as using pacman to install that software and symlinking any config files you want to their relevant directories, if any.
2018-12-07 23:47:43 +01:00
figlet
vim
neovim
httpie
rsync
git
tig
diff-so-fancy
tmux
nodejs
npm
yarn
crystal
shards
llvm
rustup
ansible
docker
docker-compose
bind-tools
pacman-contrib
nginx-mainline
jdk-openjdk
texlive-core
texlive-science
texlive-humanities
texlive-fontsextra
texlive-latexextra
texlive-bibtexextra
minted)
Reference in New Issue Copy Permalink