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
I get the following crash at the end of building the Max stuff for Jamoma:
build.rb:151:in `chdir': No such file or directory - /Applications/Max 6.1/packages/testpackage/ruby (Errno::ENOENT)
I get this crash, presumably, because I don't have the testpackage installed there -- this is not where user packages are supposed to be installed. User packages should be installed at ~/Max/Packages.
It would also be better if the script checked if the script exists instead of crashing. Or at least wrap this block in a "begin - rescue - end" block.
I guess we should look for the testpackage in Applications/Max 6.1 (provided that we are on OSX), as well as ~/Max/Packages. I don't necsessarily agree that Packages are not supposed to be installed in /Applications/Max 6.1/packages, that's what I'd do if I want to make them available for all users on a Mac with several users.
The text was updated successfully, but these errors were encountered:
In a perfect world, everything in the Max folder should be considered read-only. The permissions model of OSX, for example, is that this folder should not be writable. It is a slow-moving process over the last number of years, but Max is slowly adapting to this model.
The "correct" location for packages shared amongst all users should then be /Users/Shared/Max/Packages -- except that in our oversight we didn't implement that (yet). I'll create a ticket for at C74.
Quoting mail from @tap :
Quoting mail from @hems :
I guess we should look for the testpackage in Applications/Max 6.1 (provided that we are on OSX), as well as ~/Max/Packages. I don't necsessarily agree that Packages are not supposed to be installed in /Applications/Max 6.1/packages, that's what I'd do if I want to make them available for all users on a Mac with several users.
The text was updated successfully, but these errors were encountered: