< ^ txtWed Aug 5 07:29:31 EDT 2015 Slept well. Sunny today, and supposed to top out at seventy-nine. I have an ophthalmologist appointment this morning. Goals: Work: - Finish rent increases Done. Home: - Work on pocket-size Swords & Wizardy: WhiteBox Done. I ordered eye glasses on line. We'll see how that turns out.... I couple of days ago () I asked about GNU Stow. I still don't see the point of it. I understand that it's useful to keep your dot files in version control, and sym link to them; I already do that myself. What I don't understand is how stow helps. https://news.ycombinator.com/item?id=8487840 The stow directory is assumed to be the value of the "STOW_DIR" environment variable or if unset the current directory, and the target directory is assumed to be the parent of the current directory (so it is typical to execute stow from the directory /usr/local/stow). Each package given on the command line is the name of a package in the stow directory (e.g., perl). By default, they are installed into the target directory (but they can be deleted instead using "-D"). Hmm. OK. So I guess each directory under the stow directory is like a batch of sym links, so you can do `stow foo` and all the files in foo/ will be sym linked. I guess that's a little useful, or maybe slightly more than a little if you're constantly jumping onto new boxes where you haven't set up your sym links before. Still, kind of marginal. Not for me, I guess.
< ^ txt