## Specifications for creating add-ons for CTKArch 0.5

CTKArch 0.5's addons are squashfs archives created with mksquashfs, to put in the "addons" folder of the partition with the CTKhome label.

Any file included in an add-on replaces the genuine one in the base live system.
Keep this in mind, and avoid adding useless or empty files !
An add-on can change everything in the live system.

If you want to run things during boot, here are your options :
(do not replace initscripts : addons may conflict)

- To load kernel modules or specify module options, include a /etc/modprobe.d/something.conf file.

- To execute something as soon as the root is mounted, include a /addons/earlyrc/rc.something (avoid using this, if you don't need to modify the system before its bootup)

- To execute something after the daemons are started (before Xorg is launched) include a /addons/rc.something : to run daemons, or other...

To automatically start something at the graphical session (in user "arch), add a /addons/xsession/something.sh script

Addons creation is guided by the script supplied in /addons/mkaddon


The add-on's name MUST follow this syntax to be detected at bootup :
addon-(ask or noask)-(addon's name)-(installable ou nothing).sqfs

ask or noask : do we want to be asked if the addon must be used (mounted) at bootup ?
addon's name : should contain only letters, numbers, and some other chars. (a-Z 0-9 _ -), even if some more chars should be ok.
installable : adding 'installable' at the end of the addon's name will cause the installer to ask if it must be installed. Don't do this with an add-on designed to run in live only.

Example :

addon-noask-cups_drivers-all-installable.sqfs :
This addon just adds files.
It is installable because using it is like installing packages.

Upload your add-ons that can be useful to other people and send me the links, they will be put on the website !