-
Notifications
You must be signed in to change notification settings - Fork 257
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
Conditionally use Homebrew location for Spin plugins and templates #1494
Conversation
I don't know much about homebrew but this doesn't seem right to me. If I install e.g. iTerm from homebrew and spin from source, will spin see |
@lann This installs the plugins to |
Ohhh so the formula creates those dirs? I have no opinion then 😅 |
Yes exactly. In the formula
|
Issue added to developer documentation repository Re: documenting this work fermyon/developer#612 |
… plugins and templates Checks if Spin was installed with brew package manager and does plugin and template opperations in a directory inside the HOMEBREW_PREFIX directory Signed-off-by: Kate Goldenring <kate.goldenring@fermyon.com>
Signed-off-by: Kate Goldenring <kate.goldenring@fermyon.com>
Signed-off-by: Kate Goldenring <kate.goldenring@fermyon.com>
The current experience for installing spin is to either use the install script or build from source. Users should be able to install Spin using their favorite package manager, such as Homebrew. #641
I am working on creating a
fermyon-spin
Homebrew formula. Homebrew is sandboxed such that you can only install into a subdirectory of$HOMEBREW_PREFIX
(/opt/homebrew
on ARM macOs and/usr/local
on Intel macOs ). The formula installs default plugins and templates to the$HOMEBREW_PREFIX/etc/fermyon-spin
directory.The plugin and templates systems look at
$XDG_DATA_HOME
or more specifically$HOME/Library/Application Support
for macOS. This updates them to look for the existence of a brew installation of Spin and if exists, use the$HOMEBREW_PREFIX/etc/fermyon-spin
directory for plugins and templates.If a user has a brew installation of spin and another installation or local execution, there could be duplication of plugins and templates, with each executable using their expected directory