Four more years. :)

It seems that the ID database contains the full path to the directory where mkid was run. This fact is normally hidden because the query tools like lid reproduce the relative paths.

However, suppose that the whole directory is moved somewhere. The query in the relocated directory then produces references (either relative or absolute) to the original locations.

This is particularly annoying in situations where you are working with the same directory through different views (via symlinks or mounting).

In the case of an actual move, the behavior is completely useless because the file references do not resolve!!!

mkid should not care about the path from the root directory to the current directory and only concern itself with relative paths.

A project with an ID file should be relocatable anywhere in the filesystem tree without the ID file becoming invalid.