Yeah, `mix deps.get` would create the lock file if there isn’t one, but I also believe it would not update it unless you also change your deps. If that isn’t the case I would also argue that’s a bug (i.e. —frozen-lockfile would be implicit. An exception is where we change the lock file format, e.g. recent hex checksum changes.)
> On 17 Mar 2020, at 16:06, Alessio 'Blaster' Biancalana > <[email protected]> wrote: > > Hi José, > Wow, this is an unexpected turn of events. :-D I will track if it happens > again, sometimes my provisioning scripts (ansible roles and stuff like that) > find local modifications in my repos so it definitely gets updated. I will > come back with a more detailed analysis then, thank you for the kind reply! > > Alessio > > On Tue, Mar 17, 2020 at 4:01 PM José Valim <[email protected] > <mailto:[email protected]>> wrote: > AFAIK, mix deps.get doesn't update the lockfile. If it does, it is a bug. :) > > On Tue, Mar 17, 2020 at 3:54 PM Alessio Biancalana <[email protected] > <mailto:[email protected]>> wrote: > Hello, > It's my first time proposing a feature for a programming language so I don't > know how to deal with it and I hope to do it right :-) > > Coming from other ecosystems I saw that some platforms offer a way to avoid > updating the lockfile while downloading dependencies for a project, mainly > for software delivery and continuous integration purposes. One example of > this is the `npm ci` command, or `yarn install --frozen-lockfile` command, > for JavaScript projects. > > I love the idea to provide an option to operate with a project avoiding > generating new files or modifying existing ones, so I was thinking about > adding something like `mix deps.get --ci` or `mix deps.get > --avoid-lockfile-update`. I basically didn't want to steal the "frozen > lockfile" name, even if it is nice :-D > > From my point of view this could be a nice improvement, looking forward to > hearing from you, > > Alessio > > > -- > You received this message because you are subscribed to the Google Groups > "elixir-lang-core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elixir-lang-core/7538c297-6b3a-4d63-9324-4a1bd00b0cbe%40googlegroups.com > > <https://groups.google.com/d/msgid/elixir-lang-core/7538c297-6b3a-4d63-9324-4a1bd00b0cbe%40googlegroups.com?utm_medium=email&utm_source=footer>. > > -- > You received this message because you are subscribed to the Google Groups > "elixir-lang-core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elixir-lang-core/CAGnRm4%2BFoCt%2BXQdTr-E-RWX%2BLy%3DuR%3DzTupJX8UGoFOq7rV9TQg%40mail.gmail.com > > <https://groups.google.com/d/msgid/elixir-lang-core/CAGnRm4%2BFoCt%2BXQdTr-E-RWX%2BLy%3DuR%3DzTupJX8UGoFOq7rV9TQg%40mail.gmail.com?utm_medium=email&utm_source=footer>. > > -- > You received this message because you are subscribed to the Google Groups > "elixir-lang-core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elixir-lang-core/CAK6%2BgZJWU76JtqgCKF8G2%2B5BO0Uc8f0p2%3D7pkR1PerrDrRsa7g%40mail.gmail.com > > <https://groups.google.com/d/msgid/elixir-lang-core/CAK6%2BgZJWU76JtqgCKF8G2%2B5BO0Uc8f0p2%3D7pkR1PerrDrRsa7g%40mail.gmail.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/A06806CB-0ED7-4DD2-B432-5C71294C1997%40wojtekmach.pl.
