-
Notifications
You must be signed in to change notification settings - Fork 279
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
Installer issue with existing bash profile #43
Comments
Haven't seen the details but Macport installer does something very similar. Could be useful. See the function write_setting() in http://trac.macports.org/browser/trunk/base/portmgr/dmg/postflight |
bah - this issue is actually arisen from my background... I didnt realize that some people use .profile to store their configuration - I thought everyone used .bash_profile... not to worry, its just a case of changing some of the installer code to check for a .profile as well as .bash_profile. |
All peace :) |
doh - tottaly forgot this was outstanding... will get to it in the next few days. |
Updated installer profile checking. Closed by c4f020afda7f1ab1fb0002fa10d3e2dec8317858 |
Imported from GitHub: http://github.com/dpp/liftweb/issues/43/find |
Imported from Assembla: http://www.assembla.com/spaces/liftweb/tickets/43 |
The Liftweb installer for Mac OS X generates a .bash_profile file whether .profile exists already or not. As a result of this, the shell will ignore the preexisting environment variables defined by .profile. The installer should detect the presence of .profile, and perform an append operation instead.
The text was updated successfully, but these errors were encountered: