PerUser Licensing question

We avoid DMG format because it's proprietary, field techs can't simply double-click a DMG "package". Several twists on loop scripts, here's one that was stolen from several gurus on this list... ;)

https://jamfnation.jamfsoftware.com/discussion.html?id=11

I'm not a huge fan of the dmg format myself, but in this case, unless you plan on making this pkg ultra portable, as in, something you can deploy from ARD as well, it might be easiest to just go with using FEU/FUT as LSInNY suggests. The license file that gets captured in your currently logged in home folder would remain when packaging it up as a dmg, but Casper Suite uses it as a wildcard and will simply place it in all user home directories in the same path (for ex, /Users/*/Library/Preferences/) if you check the FEU option. It does something similar with the FUT option, but instead copies it to the same general location in the System User Template. That means any newly created accounts from that point will get the license file.

As suggested, you can also split this up into 2 packages. a .pkg for your application install and a .dmg for just the license file using FEU/FUT. However, depending on the app you're talking about, that may be overcomplicating things.

And lastly there is don's suggestion of creating a single .pkg installer, but one that uses a postflight or postinstall script to copy the license file from a /tmp/ location into all user home folders on the system.

While there may be some variations on these, those are the primary ways most here are solving the issue of getting files into the user space. The first 2 are using built in Casper Suite processes, but they require the use of a dmg format. The last is a special process involving a custom .pkg install and embedded script to handle it.

Thank you for the responses guys, the application i'm working on is Sublime Text 2. I'm going to play around with both suggested options.