You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we are using the file systems order when creating tar files (for e.g. Git dependencies). We should at least provide the --sort flag to the tar command:
--sort=ORDER
When creating an archive, sort directory entries according to ORDER, which is one of none, name, or inode.
The default is --sort=none, which stores archive members in the same order as returned by the operating system.
Using --sort=name ensures the member ordering in the created archive is uniform and reproducible.
Using --sort=inode reduces the number of disk seeks made when creating the archive and thus can considerably speed up archivation. This sorting order is supported only if the underlying system provides the necessary
information.
Right now we are using the file systems order when creating tar files (for e.g. Git dependencies). We should at least provide the
--sort
flag to the tar command:Code that has to be adjusted:
npmlock2nix/internal.nix
Line 77 in a91bc6c
It is worth checking what other options we should be setting. Perhaps nixpkgs already has this solved for us.
The text was updated successfully, but these errors were encountered: