skyvine / home-setup Goto Github PK

This should be done for the sake of portability and cleanliness.

The script will not function properly if the dotdir variable in config.scm is set to be outside of the staging area; there is a comment noting this, however neither users nor developers can be trusted to read the comments. =)

The script clones directly into your home directory. However, this can be problematic as home directories generally come installed with some reasonable default files (eg, .bashrc), and even if they don't many programs may create files in the home directory before the script is run (eg, .bash_history). This gives a compelling reason to clone into a stage, do all of the setup work, and then move everything into the home directory. This approach is also cleaner in general.

While the code is split between multiple files, this modularization is handled by merely loading files. The scripts should be modified so that they take advantage of Guile's module system.

For the sake of performing distro-specific actions (such as installing and/or configuring packages), a mechanism for identifying the current distribution and configuring distro-specific actions should be created.