If this is me, you can cite me with no problem. I do not think json has to be the easiest format, but it could work.
I think there is a lot of question that would need to be answered about what is needed from the outside build system before we get to defining an API here though. I am open to being told i am wrong of that :D On Wednesday, 21 April 2021 at 09:48:45 UTC+2 [email protected] wrote: > > The larger question I want to ask is > What is the way to get dependency information from outside elixir. > > Use case > for build tools wanting to limit network access and encourage > reproducibiliy. For example if there was a way to find out what the > dependencies are and how to fetch them, this job could be done outside of > mix. A tool with a global store could keep deduplicated version of the > dependencies and only fetched the ones that changed. Mix does that already > of course, but it's based on an using it's own way to store dependencies. > > Current barriers. > The mix.lock file format is undocumented and subject to change at any time. > Smaller question: are there plans regarding the format? Changes? How > stable is the current format? > > Potential solution > Would an api from the cli make sense? > Something like mix deps.list outputting some json format maybe? > (note this idea is not mine and i'm not sure the person having it wants to > be cited) > -- 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/28077451-fb4e-4336-b33e-17043144ce9cn%40googlegroups.com.
