Please write keyfile files in reproducible (sorted) order
Adding a new entry in a keyfile database will tend to append it, either to the end of the file if the section doesn't exist, or to the end of an existing section if the section exists but the key doesn't.
This makes the contents of a keyfile database dependent on the order of insertion. I'd like to have the contents in a deterministic, reproducible order; this helps with both reproducible builds and version control.
Section names should be versionsorted, and within a section, key names should be versionsorted. (versionsort will sort "10" after "9" and before "11", rather than sorting numbers as strings.)
Edited by Josh Triplett