Re: Installing to users Home folder using Packages
Re: Installing to users Home folder using Packages
- Subject: Re: Installing to users Home folder using Packages
- From: Howard Moon <email@hidden>
- Date: Wed, 04 Sep 2013 07:35:22 -0700
Those should probably be placed inside the bundle itself, in Contents/Resources, shouldn't they?
If they are intended to be modified, then they can be copied to the user's home directory from the app itself, at some appropriate time when running. That's the way we do it, anyway.
-Howard
On Sep 4, 2013, at 7:28 AM, James Pritchard wrote:
> It's not software we install to the users home folder but additional sample files.
>
> On 04/09/2013 15:21, Greg Neagle wrote:
>> Why do you need to do this?
>>
>> I would not want to use/support your software in an enterprise environment where:
>>
>> 1) There may be multiple user accounts on a machine
>> 2) User accounts might come from a directory service and therefore have no "footprint" on a machine when your software is installed.
>> 3) The user installing your software might be a site administrator, and not the user who will be using your software.
>> 4) The software might be installed by an automated process and there might be no user logged in at all at the time of install.
>> 5) A machine might be set up and configured _before_ the main user's account is created; the main user's account may not even exist at the time of the installation of your software.
>>
>> Software should not _require_ the installation of anything in a user's home directory.
>>
>> -Greg
>>
>> On Sep 4, 2013, at 3:32 AM, James Pritchard <email@hidden> wrote:
>>
>>> Up until now we've been using PackageMaker to put together our installs but looking to make a change to use Packages for our next software release.
>>>
>>> An issue we had using PackageMaker was with installing to the users Home folder. Our solution was to install to the /tmp folder and then copy the files across in a post flight script. Can anyone tell me if there a way of installing to the Home folder in Packages, or should I just carry on using my existing post flight script.
>>>
>>> Thanks,
>>> James
>>> _______________________________________________
>>> 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
> _______________________________________________
> 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
_______________________________________________
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