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
It would be cool to have lockfiles like .melange.lock that work similar to Cargo.lock.
With a configuration like this:
environment:
contents:
repositories:
- https://dl-cdn.alpinelinux.org/alpine/edge/main
- https://dl-cdn.alpinelinux.org/alpine/edge/community
packages:
- alpine-baselayout-data
- busybox
- make
- go
- git
- ca-certificates-bundle
The lockfile would contain the resolved versions for make, go, git, etc and help achieve reproduce builds even if one of the packages was updated in alpine in the meantime.
The file could be generated with a command like melange update and toml would probably be a good fit since it works well in git diff and has good machine readability.
The text was updated successfully, but these errors were encountered:
I have a different plan for this, where you run a command and it generates a local repo containing the packages used. You could then use this “lock repo” for this purpose. That way there are no ambiguities with the packages.
hi!
It would be cool to have lockfiles like
.melange.lock
that work similar toCargo.lock
.With a configuration like this:
The lockfile would contain the resolved versions for make, go, git, etc and help achieve reproduce builds even if one of the packages was updated in alpine in the meantime.
The file could be generated with a command like
melange update
and toml would probably be a good fit since it works well in git diff and has good machine readability.The text was updated successfully, but these errors were encountered: