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
{{ message }}
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
It caught me off guard that running ./configure wrote things to my home directory. As I had a old install of mason it was throwing errors that didn't make sense, which lead me to notice this ~/.mason directory.
If this is going to remain in the ./configure script should it be clear the the user that it is writing to and looking for these directories?
The text was updated successfully, but these errors were encountered:
Ideally we could use a local mason if no ~/.mason already exists to avoid writing to ~. As far as nvm what about trying to remove the node.js build dependency altogether?
It caught me off guard that running
./configure
wrote things to my home directory. As I had a old install of mason it was throwing errors that didn't make sense, which lead me to notice this~/.mason
directory.If this is going to remain in the ./configure script should it be clear the the user that it is writing to and looking for these directories?
The text was updated successfully, but these errors were encountered: