[ new ] Support for dumping a package's install location #3381
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Historically I have hard coded assumptions about where Idris will install a package when
idris2 --install
is called. This works, but it's fragile, inconvenient, and far from obvious.See, for example, this snippet from one of my C support library Makefiles:
This PR introduces
idris2 --dump-installdir
which could make the above Makefile snippet much more reasonable:While I was adding
--dump-installdir
anyway, I also used it in the existing NixbuildIdris
function to better support a "Pack-ism" where C support libraries are installed to the./lib
folder and Pack takes care of the rest. NowbuildIdris
also takes care of the rest.Should this change go in the CHANGELOG?
implementation, I have updated
CHANGELOG_NEXT.md
(and potentially alsoCONTRIBUTORS.md
).