Ideally I'd like to see ArchBlocks turn into a combination of:
-
Learning tool (easy way to onramp into Arch Linux in companion to the Beginner's page on the wiki, for example)
-
System specific fixes/tweaks (this is the SYSTEM_* file that fixes the problem for that specific laptop/wifi-card/etc).
-
Recipes for installing both common and uncommon configuraiton (e.g. everything from an unencrypted ext4 single partition system to a fully encrypted swap/root/home 4 partition setup).
To this end I'd really like to have people submit new recipes (the aforementioned FILESYSTEM variants) as well as system specific blocks.
I want to keep the blocks more or less completely swappable. So no weird inter-block dependencies (this is the reason for the FILESYSTEM_PRE_* functions).
Try to be concise but clear in naming.
I'd like to avoid having a lot of block types. Right now it looks like the following list, but I'm considering subsuming the Phase 2 apps list (desktop, power, et al) under a prefix such as APPS or UTILS. Not sure yet. Feedback welcome.
PREFLIGHT FILESYSTEM BASEINSTALL
LOCALE TIME DAEMONS HOSTNAME NETWORK KERNEL RAMDISK BOOTLOADER
SYSTEM
DESKTOP POWER UTILS AUDIO VIDEO WARN XORG
HOMESETUP
POSTFLIGHT
I'd recommend creating a fork of this repo and test your blocks there prior to submitting them back.
I'm available on github/email/twitter/etc. almost universally under [email protected] / @ethanschoonover / ethanschoonover. I'm either ethanschoonover or altercation on most IRC networks.