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: Don Montalvo <email@hidden>
- Date: Wed, 04 Sep 2013 12:30:07 -0400
I guess it depends on the situation. AAMEE is a big old hunk of duct tape, no? Greg has provided the Mac community with many duct tape solutions, very much appreciated by not only us, but also the vendor. It's all part of the process - keep our users productive and work to make things better.
InsiderSoftware listened, they actually had a series of calls with our team (last gig) and they're working to implement all-user defaults capabilities.
BinaryAge (TotalFinder) is a smaller company, their engineer turned around the same in a much shorter time.
Many other examples...different results, always the same goal.
So yea, taking a stance is all good, but the last thing we ever want to do is disrupt production, risk missed deadlines, etc. Liberal use of duct tape isn't a bad thing, if you circle back with a proper fix when one is available.
On Sep 4, 2013, at 11:47 AM, Conor Schutzman <email@hidden> wrote:
> Bad habits on the part of the software developer SHOULD NOT lead to bad habits on the part of the packager.
>
> The trick of moving files into home via LaunchAgent is (IMHO) the best compromise. But if the vendors are as open to feedback as you say, why not push back as to their poor coding habits?
>
>
>
> On Sep 4, 2013, at 7:51 AM, Don Montalvo <email@hidden> wrote:
>
>> Greg as usual you're right. :)
>>
>> However there are a good number of vendors (FontAgent Pro 5) that still have defaults settings that are managed per-user instead of all-users. There are other settings that are not manageable by defaults but that's another thread. ;)
>>
>> We work with vendors all the time, most listen (this one listened), most turn around fixes quickly (we'll see if/when this vendor will provide the necessary change)...some don't, so until they do the ability to deliver stuff to (~) is unfortunate reality.
>>
>> I'm BCC'ing the InsiderSoftware folks in case they want to chime in...
>>
>> Good to know Packages.app offers this supported function. :)
>>
>> Don
>>
>> 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
>>>
>>> James Pritchard 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