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
Some packages are archived along with source code or code for stdlib functionality etc. It might be useful to be able to have an "install" config variable which would be a directory for installed code to be saved at (this could also be overwritten by the package in the config?).
A good example is node / npm which comes with a node executable which is a single binary, and then npm which is a javascript script which relies on code from the packaged lib/, share/ and cinclude to be in a known location.
This would also be useful for protoc which includes some includes/ proto files for useful proto definitions.
The text was updated successfully, but these errors were encountered:
Some packages are archived along with source code or code for stdlib functionality etc. It might be useful to be able to have an "install" config variable which would be a directory for installed code to be saved at (this could also be overwritten by the package in the config?).
A good example is node / npm which comes with a
node
executable which is a single binary, and thennpm
which is a javascript script which relies on code from the packagedlib/
,share/
andcinclude
to be in a known location.This would also be useful for
protoc
which includes someincludes/
proto files for useful proto definitions.The text was updated successfully, but these errors were encountered: