Replies: 1 comment 2 replies
-
It could be implemented, but... I'm curious, what's your use case? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello all!
I'm writing a module. Now, when I install a binary using
inst <binary> [<optional destination>]
, the binary gets installed. Including the dependencies (libraries) of the binary.I found out, this library dependencies resolution step doesn't happen at the same moment as the installation of the binary. I guess that the image first gets populated with all the files/binaries that modules install in one way or the other, and at the end, just before the image gets packed, there is a loop over all the binaries in the image which installs all the library dependencies.
Would it be possible to only install the dependencies of a binary but not the binary itself?
As an example:
Then
inst_deps_only /bin/python
would install:Beta Was this translation helpful? Give feedback.
All reactions