| Commit message (Collapse) | Author | Age |
|\ |
|
| | |
|
|\ \
| |/
|/| |
|
|/
|
|
|
| |
This is a weird YAML gotcha, and it seems worth mentioning in the readme
since Dotbot users are likely to run into it.
|
| |
|
|\ |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previous to this patch, having a config like the following would not
work properly:
- link:
~/a: ~/b
This was because the '~' was expanded on the left hand side (the link
target), but not the right hand side (the link source). It was necessary
to use a workaround like this:
- link:
~/a: $HOME/b
This was because variable expansion was being done, but user expansion
was not being done.
This commit adds support for using '~' in the link source.
|
|
|
|
|
| |
This change was suggested by Brian Jacobowski
<bjacobowski.dev@gmail.com>.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Prior to this patch, the following config led to incorrect behavior:
- link:
~/.folder/file:
path: file
create: true
relative: true
relink: true
Prior to the change, running the config the first time would result in
expected behavior. However, running the config for the second time would
result in deletion and re-creation of the link (even when the link is
correct).
This patch improves the interaction of relink and relative, taking
relative paths into account when checking the validity of existing links
in the `_delete()` method.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This feature was implemented with feedback from Aleks Kamko
<aykamko@gmail.com> and Casey Rodarmor <casey@rodarmor.com>.
|
|
|
|
|
|
|
| |
This commit adds an option to the extended configuration syntax for
linking files and directories. Enabling the relative option makes it so
that symbolic links are created with relative paths instead of absolute
paths.
|
| |
|
|\ |
|
|/ |
|
| |
|
|\ |
|
| | |
|
|/ |
|
| |
|
|\ |
|
|/
|
|
|
| |
The test suite has been slightly modified to allow running tests without
Vagrant on Travis.
|
|
|
|
|
| |
This patch removes a stray print statement that was causing problems
with Python 3.
|
|
|
|
|
| |
This patch makes Dotbot provide better error messages when parsing JSON
files.
|
|
|
|
|
|
| |
This patch reverts the changes to the README made in
57265f78b4e4f6ca67393f55b2b08f6f45a02ff1 and makes it so that Dotbot
supports JSON files with tab characters.
|
| |
|
|
|
|
|
|
|
| |
Casey Rodarmor <casey@rodarmor.com> pointed out that Dotbot parses JSON
files as YAML. The YAML format doesn't allow tab characters, which are
normally allowed in JSON. This patch adds a note about this to the
README.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
In our use case, we are *not* reading arbitrary input that could be
malicious. Still, because we know that what we're reading is made up of
only dictionaries and lists and not arbitrary Python objects, we might
as well use the more restrictive `safe_load` function rather than the
`load` function.
|
| |
|
|\ |
|
|/ |
|
|
|
|
|
|
|
| |
The information that was added in
115210ab1725fcb3e5dbe48d4488f71389704e95 was removed in
4ed3ffc411f662f66082dad91d4ae4ff83c04f7b when reorganizing the README.
This commit restores the information.
|
| |
|
|
|
|
| |
This feature was proposed by Brian Knobbs <brian@redlattice.com>.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This commit adds an option to the extended configuration syntax for
linking files and directories. The relink option is a safe alternative
to forcibly linking that only removes broken symbolic links, so it
cannot result in data loss.
|
|\ |
|
|/
|
|
|
|
| |
Check if entry to force-create (delete) is a symlink and if so, simply
unlink it. Don't try to run rmtree on the underlying directory, which
will fail anyway.
|