Open Tina-otoge opened 6 years ago
ln
is much better than cp
imo, it takes so much time to update the config files with having to copy them everytime.
maybe use ln
and tell people to put cp
instead if they want to make their own configs?
As I described the difference between the two, if you symlink the files from this repo and do modifications, and then want to update the repo without overwriting your local changes (ie. you are not me and modified a file not stored in one of the "custom" scripts), copying makes more sense.
Because if you symlinked from the repo, you won't be able to pull after modifying, that's why I said: make an option available to use either ln
or cp
rather than forcing one over the other
well in this case you can just make a new branch and push it to another remote
Add a script in the repository to interactively install the configuration files per group.
This should significantly improves deployment time.
(optional) Include a short documentation of what each group affects when asking to install them, so the user does not have to read the configuration files to know what they do.
Languages to use
Features wanted
cp
orln
: