summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2022-05-24Use format 1 without mtime in the example hooksAdam Spragg
2022-05-24Add post-merge git hook.Adam Spragg
It's the same as the post-checkout hook, doing the same job. I thought about symlinking instead of copying, but something doesn't sit quite right about that.
2022-05-24Make example hook shell scripts executableAdam Spragg
2022-05-24Abort commits during conflicts if differences existAdam Spragg
If the user is running `git commit` to resolve a conflict, it's dangerous to just save the metadata from the filesystem. It's possible that they just fixed a conflict in the metadata file, but didn't update the on-disk metadata to match. (I know it's possible, because I did this!) Our normal mode of operation, of just saving the metadata during a commit to match whatever's on-disk, would wipe out their careful conflict resolution! (On the other hand, just overwriting the on-disk metadata might not be the best idea either.) But the point of a conflict is that the changes between two different branches *can't* be resolved automatically, and requires manual intervention. Given that situation, asking them to resolve the difference manually seems to be the most obvious option.
2022-05-24Change "compare" output from MSG_QUIET to MSG_NORMAL.Adam Spragg
Compare output is... just output. We shouldn't need to pass two "-q" options to shut it up. Likening the metastore MSG_* levels to syslog() LOG_* levels, MSG_DEBUG works like LOG_DEBUG, and the WARNING/ERROR/CRITICAL also have similar roles. That leaves MSG_NORMAL as the equivalent of LOG_INFO, and MSG_QUIET as the equivalent of LOG_NOTICE. LOG_NOTICE is documented as for "normal, but significant, condition" which tracks what MSG_QUIET is for - things that aren't errors, but that you want to know about even when you've asked for quiet. Whereas the output of "compare" is just regular output. Finding a difference isn't a significant condition - it's exactly what you've asked it to look for.
2022-05-24Return non-zero exit status if "compare" finds differencesAdam Spragg
This makes `metastore` more useful in scripts, just to check if it found anything, in the same way as `diff` and `grep`. Note that POSIX requires that EXIT_SUCCESS is 0, and EXIT_FAILURE is 1, so I've defined EXIT_DIFFERENCES as 2 which, while different from the values `diff` and `grep` use (1 for finding something, 2 for errors), maintains a certain amount of backwards compatibility with previous versions of metastore.
2022-05-24Make "--no-mtime" apply to "dump" actionAdam Spragg
2022-05-24Add ability to not save mtime in metadata filesAdam Spragg
If you're storing metadata in a version control system with multiple branches, mtime differences are going to produce a whole bunch of conflicts that you likely don't care about. This allows you to not save mtime and avoid those. Note that we use a sentinel value of -1 for the mentry `mtimensec` field to indicate this in the data, as all values of `mtime` are theoretically valid, but `mtimensec` must always be between 0 and 999,999,999 in the real world. I'm not 100% sure about the mechanism for selecting this feature. The legacy behaviour for metastore was to save mtimes in the metadata files, but ignore them for compare/apply by default, with a `--mtime` option to use the mtime data. Keeping the legacy behaviour for backwards compatibility, but adding a `--no-mtime` option to ignore mtimes when saving felt like a reasonable way of making this happen, but something about it doesn't feel great. Maybe I just didn't figure out how to make the documentation clear enough. ¯\_(ツ)_/¯
2022-05-18Sort entries in Format 1 files by path, ASCIIbetically.Adam Spragg
This ensures that the files are stable, and not subject to the order in which the OS returns directory entries. This should prevent unnecessary changes, and therefore unnecessary merge conflicts.
2022-05-18Add ability to read Format 1 metadata filesAdam Spragg
2022-05-18Add ability to write Format 1 metadata filesAdam Spragg
2022-05-18Add documentation for new Format 1Adam Spragg
2022-05-18Add -r/--format option to pick the format to save asAdam Spragg
Only version 0 is supported here.
2022-05-18Build metastore.txt as part of `make all`Adam Spragg
2022-05-18Separate format-specific read/write logic into own functionsAdam Spragg
2022-05-18Reuse already calculated end-of-buffer pointerAdam Spragg
2022-05-18Make buffers that are read from `const`-correctAdam Spragg
2022-05-18Label file Format 0 explicitly as Format 0Adam Spragg
2021-04-08Fix "changing owner" message to show owner instead of group.HEADmasterPrzemyslaw Pawelczyk
2021-04-07NEWS: Mention normalize_path() bugfix.Przemyslaw Pawelczyk
2021-04-07AUTHORS: Add Jürgen Bubeck.Przemyslaw Pawelczyk
2021-04-07Fix path normalization for the case of CWD being the root directory (/).Jürgen Bubeck
Previously metastore would fail if running from / and paths were given: $ pwd / $ metastore -d bin lstat failed for .bin: No such file or directory Now it works properly: $ metastore -d bin | head -1 lrwxrwxrwx root root 2018-08-17 16:31:23.120322532 +0200 ./bin/hostname Signed-off-by: Przemyslaw Pawelczyk <przemoc@gmail.com>
2018-09-08Fix conversion specifiers in "Failed to {malloc,strdup}" messages.Przemyslaw Pawelczyk
2018-09-08Add missing argument to "Failed to get metadata for %s\n" message.Przemyslaw Pawelczyk
2018-02-19Support building with empty -DNO_XATTR= (equivalent to -DNO_XATTR=0).Przemyslaw Pawelczyk
2018-02-19Makefile: Support NO_XATTR variable.Przemyslaw Pawelczyk
2018-02-19Support building with no extended attributes support.Przemyslaw Pawelczyk
Support building with no extended attributes support when NO_XATTR macro is predefined to non-0 value (e.g. put -DNO_XATTR in CFLAGS).
2018-02-18utils.h: Introduce new verbosity level: MSG_WARNING.Przemyslaw Pawelczyk
2018-02-18metastore.c: Version information cannot be suppressed.Przemyslaw Pawelczyk
2018-02-18metastore.c: Print usage to stdout if help is requested.Przemyslaw Pawelczyk
Also change level of usage message shown after critical one to error, so it can be suppressed without hiding critical one if desired (-qqq).
2018-02-03README.md: Create a symlink to README.Przemyslaw Pawelczyk
README is actually written in markdown, but I don't like .md extension. README.md is here only for better experience of web viewers of the repo, it's set to be not exported by git archive and won't be present in released tarballs. BTW if GitHub is offline, you can use following unofficial mirror: http://repo.or.cz/metastore.git (It also renders README.md file, that's why I mentioned it here.)
2018-02-03Update copyright notices.Przemyslaw Pawelczyk
2018-02-03Add SPDX License Identifier to all source files.Przemyslaw Pawelczyk
The Software Package Data Exchange (SPDX) is a good initiative, it has matured over time and deserves accelerated adoption in open-source. https://spdx.org/learn https://spdx.org/using-spdx https://spdx.org/license-list
2018-02-03Slightly reformat and modernize GPLv2 only license notices.Przemyslaw Pawelczyk
Reformat second paragraph for better look. It had awkward line wrap. Modernize third paragraph. No need to send letters to FSF in Boston.
2018-01-23Fix documentation: integers are stored in little-endian byte order.Przemyslaw Pawelczyk
David misdocumented read/write int functions back in commit 5fed2f9169fdd0585cc83ff0fa8210d97da77cb2 (2007-05-19) and later it probably got copy-pasted to the documentation of file format.
2018-01-23Fix sparse warning: Variable length array is used.Przemyslaw Pawelczyk
Avoid using VLAs when it is not really needed, especially in cases like this one here, when possible array size is very limited (1-8 bytes).
2018-01-23Fix sparse warning: symbol was not declared. Should it be static?Przemyslaw Pawelczyk
Declare file-scope objects or functions that do not need external linkage as static.
2018-01-23Fix sparse warnings: non-ANSI function declaration.Przemyslaw Pawelczyk
Explicitly specify void when a function accepts no arguments.
2018-01-06metastore v1.1.2v1.1.2Przemyslaw Pawelczyk
2018-01-06Makefile: Treat LDFLAGS as passed to the compiler, not linker directly.Przemyslaw Pawelczyk
2018-01-06NEWS: Mention recent PATH_MAX-related change.Przemyslaw Pawelczyk
See commit 16cde6c32fb3e0640ac01ca5d8ddea127f59106c for details.
2018-01-03Makefile: Add printvars phony target.Przemyslaw Pawelczyk
2018-01-03metaentry.c: Define PATH_MAX if it's undefined.Przemyslaw Pawelczyk
PATH_MAX is not guaranteed by POSIX to be present and some systems, like GNU Hurd, indeed does not define it. http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/limits.h.html https://www.gnu.org/software/hurd/hurd/porting/guidelines.html For now let's define PATH_MAX as 4096 (if it is not already defined), because that's how Linux defines it and it seems quite reasonable. In future dependence on PATH_MAX can be removed.
2018-01-02metastore v1.1.1av1.1.1aPrzemyslaw Pawelczyk
2018-01-02.gitignore: Do not ignore debian/ directory.Przemyslaw Pawelczyk
https://bugs.debian.org/883539 Requested-by: Romain Francoise <rfrancoise@debian.org>
2017-12-04metastore v1.1.1v1.1.1Przemyslaw Pawelczyk
2017-12-03README: Fix another typo.Przemyslaw Pawelczyk
2017-12-03README: Fix typo.Andy
Signed-off-by: Przemyslaw Pawelczyk <przemoc@gmail.com>
2017-11-24metaentry.c: Fix underallocation for xattr_lvalues.Przemyslaw Pawelczyk
Wrong type has been used for calculating size of requested memory. Underallocation happened in mentries_fromfile() code path if sizeof(ssize_t) > sizeof(int), which is true on 64-bit platforms. Reading metadata file with extended attributes entries led to corruption of metadata represented in memory on such platforms, so applying could led to corruption of metadata on disk too. Reported-by: Uros Juvan <asmpro@gmail.com>
2016-02-22metastore.c: Be more strict about arguments in compare_print().Przemyslaw Pawelczyk
That way we can avoid possible (yet not feasible in current code) NULL pointer dereference.
generated by cgit v1.2.1 (git 2.18.0) at 2025-01-23 14:33:05 +0000