| Commit message (Collapse) | Author | Age | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A couple of small changes to this function should make it more robust in
the long run:
1) We no longer filter the symlinks with find(1), instead combining
filtering and substituting in sed(1)
2) We use the absolute path (as given by readlink -f) such that we can
anchor the regular expression pattern to avoid unwanted substitution.
3) Instead of hard-coding paths we now use STOW_DIR (and STOW_DIR/.. for
the target directory)
4) To avoid unnecessary complexity, we no longer let the user override
STOW_DIR. This tool is supposed to be used with the canonical
/etc/portage/stow location
|
|
|
|
|
| |
I am unsure whether this is consistent across distributions, but for me
stow appears in Section 8 - User Contributed Perl Documentation.
|
|
|
|
|
| |
This lets the user rebuild (or restow) specific roles and will fix a
certain issue with stow refusing to unstow everything.
|
|
|
|
|
| |
I would not expect this to ever fail, but quoting the specific
invocation of id -u here silences the only shellcheck warning.
|
|
|
|
|
|
|
| |
Instead of hard-coding the stow invocation (which also had a quoting
issue), just export the STOW_DIR environment variable which stow uses
already. TARGET can be dropped because it is implicitly defined to be
the parent directory of STOW_DIR.
|
| |
|
|
|
|
|
| |
It has always been possible to add or remove multiple roles at once, and
this is now reflected in the manual.
|
| |
|
| |
|
| |
|
|
|