Re: Installing to /Users/<username>/...
Re: Installing to /Users/<username>/...
- Subject: Re: Installing to /Users/<username>/...
- From: eveningnick eveningnick <email@hidden>
- Date: Sun, 31 Oct 2010 18:08:55 +0200
> Perhaps you should take a different approach, and do what many apps do: distribute it as a drag-and-droppable .app bundle, and the first time a particular user runs your app, install your LaunchAgent.
> Since you're only installing stuff into the running user's home folder, you don't need root permissions or anything like that.
>
> What you're trying to do will not work properly if there is more than one user account on the system that wants to use your app, whereas installer per-user when the user runs your app should work for multi-user configurations.
I am sorry, i have posted this message privately (wrong button). I'm reposting it to the mailing list to make it available for everyone
Hi Dave
The problem with my app is that it needs to install some other files,
except that plist. Installer, besides creating .plist, copies some
"template" documents to the user folder (more specifically, to
/Users/<username>/Library/Application Support/MyAppName/...) and
provides uninstaller as well (an Applescript bundle).
I want to create installer, because the presence of an installer is a
sign for a user that application "does something more that just runs
when the bundle is double clicked". And if i provide only an
application bundle, the user will feel tempted to just move it to
trash when he doesn't need my application.
This plist file, that is supposed to launch my app everytime the
system starts, will cause problems (because, user had qlreqdy moved
bundle to trash, Launchd can't find app's executable - it'll pop up
that annoying message every 10 seconds).
These template documents, that i install to
/Users/<Username>/Library/Application Support/MyAppName... will take
some of the disc space like a garbage that otherwise would have been
cleaned by uninstaller, etc
I just want to make it obvious and intuitive for a user, that he
should uninstall the app the same way he installed it - using an
installer or uninstaller.
That's why i need an Installer (just like Microsoft Office does). I am
aware of that it is not recommended to install a decent application in
any other way than copying a bundle.
I am considering also a possibility to install all the files not to
user home directory, but to /Library/Application Support/MyApp... and
/Library/Launch Agents/MyApp/... , but: my application needs to manage
that plist file (it should be possible for it to create that file,
modify it or delete it). Unfortunately, the system doesn't let me to
do that - an application doesn't have enough of privileges. Maybe if i
solved this problem, i wouldnt have needed that $user variable from a
script. Although i have no idea how to modify a file in
/Library/LaunchAgents/... from an "ordinary user" application.
Can it be done somehow?
Thank again, George
_______________________________________________
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