If the user has modified the file in /etc/, it will not be removed
and a message will be printed to the screen. If the file is
unmodified, it will be removed like any other.
This uses the etcsums file for comparison of checksums. The file
is also used during installation handling of files in /etc/.
This was half-assed. I'd much prefer we keep things simple and users
use repositories for this purpose. Either full or partial forks. This
is "proper" and stores the build configuration
This is a backwards compatible change. The package manager will
for the time being /ignore/ checksums lines containing Git
repositories.
These aren't checksums and have no business living in the checksums
file. This file is now strictly for checksums. In the coming months,
this special handling will be lifted.
This adds support for both absolute and relative directories in
sources files. Relative file sources have always been supported,
this just extends it to directories.
Absolute paths to directories and files in sources is totally new.
Directories will have their /contents/ copied to the initial build
directory. The second field in the sources file can be used to set
destination location.
Checksums will not be validated for directories of any type. Absolute
file paths do have their checksums validated.
Notes:
The package manager will check to see if the source is a directory
or not. There is no need to have a trailing forward slash (though it
might make sense to enforce this anyway, we'll see).
With this change, checksums generated by the package manager will no
longer contain the second field (the basename of the file). The second
field is quite useless as ordering is already fixed.
This change is backwards compatible and existing checksums files will
containue to function as normal. As checksums are regenerated (with
updates to packages), the new format will be used.
The compatibility works via checking /only the first column/ in each
checksums file. This is the only part of the file which must match
1:1 as ordering is always the same.
Notes about etcsums:
This change also affects the etcsums file which is used for the
3-way checksum verification for files in /etc/.
Existing etcsums will simply be invalidated with the safest path chosen
(.new file is created) until they are regenerated via a package build.
Ordering is now fixed inside etcsums files. This makes parsing them
faster and more reliable.
This also fixes a theoretical bug with naming conflicts during parsing
of etcsums.
The package manager will look for an executable called 'update' in the
repository's root directory. If a KISS repository is one of many
children in a git repository, the hook will only be called once.
This hook is run /after/ a repository has been updated by the package
manager. If your repository is not using git, the hook is run immediately.
If the hook fails (exits non-zero), the package manager will also fail.
Hooks can be written in any language. No arguments are given to the executable.
Closes#174
