bryanhuntesl
I’ve got a project which depends upon another project containing protocol buffer generated files.
It’s a GRPC server project.
Is there any trick you can do to prevent a dep being locked - that is, everyone you execute ‘mix deps.get’ the latest version for the configured branch will be fetched ?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #ai
- #phoenix_html
- #elixirconf-us
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 8- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
ityonemo
use the :branch option.
Edit: Actually i"m not 100% sure this doesn’t cache a lock at get-time. If it does, you can always mix deps.update
outlog
believe it’s a feature that it locks..
you can use mix deps.update my_dependency
OvermindDL1
Correct, it’s to prevent it from, say, randomly breaking when it was just working from build to build.
axelson
As far as I know there’s no way to accomplish this directly. I’d probably either:
deps_get.shscript that ranmix deps.get; mix deps.update grpc_deppathdependency in development and add a ci task to check that the version of thegrpc_depin the lock file is the most recent versiona. Note that this requires you to have a separate local checkout of the dependency
Alternatively you could forgo a mix.lock file completely (by constantly deleting it) but I wouldn’t advise you to take that approach.
ityonemo
Aliasing certain mix tasks might work without having to write a shell script.
mergefailure
Thanks all - that was my understanding too - I just wanted confirmation that I hadn’t missed anything (future readers, this isn’t a feature request
)
@ityonemo your suggestion of aliasing deps.get is something that didn’t occur to me - I might give that a try - could be quite convenient.
ityonemo
I’d say just be careful. I just learned about it recently; Mix aliasing is wonderful but for this particular use case it could be dangerous as since it’s relatively less well known it might be forgotten to be turned off when the codebase stabilizes and shouldn’t be using it in the future.
mergefailure
I should note this is a feature branch depending upon a rapidly changing upstream feature branch - work needs to be performed on both repositories at the same tiem in order to reach PR approval stage - duly noted.