Re: Environment variable availability within post-install script
Re: Environment variable availability within post-install script
- Subject: Re: Environment variable availability within post-install script
- From: Bill Coderre <email@hidden>
- Date: Mon, 10 May 2010 14:18:13 -0700
On May 10, 2010, at 1:49 PM, Tim Streater wrote:
> On 10 May 2010 at 19:30, Bill Coderre <email@hidden> wrote:
>
>> Very important points. Here are some vague suggestions on how to cope:
>> 1) Get rid of per-user things.
>>
>> Obvious, but: Don't have your installer create per-user preference files! Put
>> "Shared" content in /Users/Shared/ or /Library/Applications Support/YourApp/
>>
>> This should take care of most things for App developers. (Yes, this is
>> different than Windows. Sorry, but you're going to have to cope with it.)
>
> Hmmm, my original question appears to have generated more responses than I expected, so I can see I'm going to have to bore people with an outline of what I'm up to.
>
> I retired a couple of years ago, and as an exercise have been recreating the features of Eudora that I happen to like. There's a couple of Eudora-replacement exercises going on but each is taking some time to come to fruition. Meanwhile, I thought I'd see whether it was possible to use Safari with some JavaScript to present an email client to the user, communicating via AJAX to a number of PHP scripts that talk to mail hosts and store data using SQLite. Where I'm at now is that it largely has the feature set I was planning for it. And we know there's anyway a desperate shortage of email clients for OS X (irony).
>
> At present my .webloc contains this URL:
>
> http://localhost/~tim/myApp/myApp.phtml?user=tim&datarootpath=/Users/tim/Sites/myAppData/
>
> which indicates where the JavaScript/PHP is stored and also where the user's data wants to reside. The PHP scripts run as user _www (I couldn't figure out if it's possible to have Apache run them as user tim - but that's OT for here anyway) so there'll be some permissions problems I haven't resolved yet. But this is basically why I arrived at needing the user's shortname and home directory path in a per-user file created by the installer.
In your case, you can probably stick to the "each user must run the installer if they want my app" plan for a while.
Eventually, you probably should bundle up all your resources and make an "application" out of it. _______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden