#lockfile decisions

8 messages · Page 1 of 1 (latest)

gentle moth
#

I am trying to package an application I'm making for nix. Nix thanks to reproducible builds requires Cargo.lock to be tracked by git.

The issue is the application is in a workspace with two libraries which as far as my research shows should not have a tracked lockfile.

I do not want to spin the libraries into separate crates outside the workspace since I dont want to deal with keeping their dependencies matched. But if its needed its needed.

What would be the best option forward here.

lucid hornet
#

For example, if your libraries have examples, standalone or in documentation, then they have runnable binaries (those examples), and thus you should commit lockfiles

#

Some people also just say to always commit lockfiles unconditionally

gentle moth
#

there are examples in the repo so I guess I'm commiting it. Are there any major problems I should be ready for.

lucid hornet
#

Not that I'm aware of, but that's because I know next to nothing about this topic

#

Get a second opinion 🙂

gentle moth
#

fun 👍