-
-
Notifications
You must be signed in to change notification settings - Fork 9.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support user set BUNDLE_USER_CACHE #17276
Comments
Why do you want this variable to be honoured? That Homebrew uses Bundler should be seen as an implementation detail. This seems like a potentially small performance improvement for developer commands in exchange for a higher change of errors occurring with cache/Bundler issues. |
I am not sure we are on the same page. Hopefully the following will add more clarity. On macOS I have setup my shell environment to follow the XDG directory spec as much as possible. To have my preferences supported by Bundler I added the So for me, supporting (I did try one quick attempt at implementing a solution but I was unsuccessful.) |
Was anything put in it/used from it? Ideally we'd avoid creating/using these sorts of directories in Homebrew at all. I agree with avoiding writing things to |
Yes. Standard looking Attached is directory listing after running the following:
|
As a side note, after clearing Homebrew gems and then reinstalling the following error is consistently flagged.
|
Setting it unconditionally to
How are you clearing the gems? |
Via I found the solution in a comment on GitHub. It wasn't clear to me how to do it otherwise. |
Yeah that's the supported way. Will check why Bundler doesn't cleanup plugins. |
Agreed. Should just be an environment variable to do so. |
On my end #17304 doesn't resolve the issue. |
What's the output of |
|
Do you have a |
No. The following is my
Output from
I don't have a config file so the config folder doesn't exist and is not created. |
Verification
brew install wget
. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.Provide a detailed description of the proposed feature
Have Homebrew Bundler honor BUNDLE_USER_CACHE path variable if it has been set by the user.
What is the motivation for the feature?
When Homebrew installs or updates vendor gems it creates or uses the
./bundle/cache
directory ignoring BUNDLE_USER_CACHE variable set in the users environment. By the doing this it negates setting the variable in the first place.How will the feature be relevant to at least 90% of Homebrew users?
It will not be relevant.
What alternatives to the feature have been considered?
No alternatives have been considered.
The text was updated successfully, but these errors were encountered: