||1 year ago|
|cmake||2 years ago|
|doc||1 year ago|
|src||1 year ago|
|test/unit||1 year ago|
|vendor||1 year ago|
|.clang-format||1 year ago|
|.gitignore||2 years ago|
|.gitmodules||1 year ago|
|CMakeLists.txt||1 year ago|
|LICENSE||2 years ago|
|README.org||1 year ago|
|compile_commands.json||2 years ago|
Config file and package tracking utility.
- Manage dotfiles and system config files.
- Selectively comment and uncomment depending on machine configuration.
- Store a list of all installed packages.
- Install packages from a stored list.
Install the example configuration
During installation, manafiles will install the example config to:
From there you can copy it to anywhere in the working directory,
the config file is searched recursively.
Everything in this list will get ignored when pulling/pushing config files from the working directory.
Currently two types of file matching are supported:
literalmatches a file or directory literally
wildcardthe asterisk matches zero or more characters
These behave similarly to a
- If the pattern starts with a slash, it matches files and directories in the working directory root only.
- If the pattern doesn’t start with a slash, it matches files and directories in any directory or subdirectory.
- If the pattern ends with a slash, it matches only directories. When a directory is ignored,
all of its files and subdirectories are also ignored.
The ignore patterns from the example config:
"ignorePatterns" : [ ".git/", "*.md", "manafiles.json", "packages", "README.org", "screenshot.png" ]
System config files
Everything in this list will be pushed to the root
/ of the system, instead of
These support the same file matching as explained in the Ignore patterns section.
The system patterns from the example config:
"systemPatterns": [ "/boot/", "/etc/", "/usr/lib/", "/usr/share/" ]
Selectively comment and uncomment
Config files can be pushed from the working directory to the system like so:
$ manafiles -Fs
When pushing files to the system, manafiles recognizes special blocks and comments or uncomments them depending on the machine's configuration. Such a block looks like this:
# >>> distro=arch hostname=arch-desktop user=anon export PATH="$PATH:$HOME/.local/bin" # <<<
This block uses all of the supported configurations,
user. These can be used in any combination and order.
If all of the given configurations match, manafiles will make sure that the contents of the block are uncommented. If any of them do not match, then manafiles will make sure that the contents of the block are commented.
The optional requirements are for the package tracking functionality.
To get the sources from the repository, run the following commands:
$ git clone https://github.com/riyyi/manafiles $ cd manafiles $ git submodule init $ git submodule update
$ git clone --recursive https://github.com/riyyi/manafiles $ cd manafiles
To compile, run the following commands:
$ mkdir build $ cd build $ cmake .. $ make # Optional. This will install the manafiles executable in /usr/bin $ sudo make install
To uninstall, run the following commands:
make uninstall will try to delete all files listed in the
install_manifest.txt file inside your
build folder. Make sure you first
check that it won't delete any important files.
$ cd build $ sudo make uninstall