Packaging Lightroom 4

Adobe's PKG installer works fine for us...double-click works, push via Casper/ARD/SCP+SSH works...

Don

The Registration file is located in /Library/Application Support/Adobe/Lightroom. I just package that file and deploy it along with the Adobe .pkg.

Just checked LWS and 4.1 shows up.

Don

Nice to hear it is working for you folks. I am going to try re-packaging it tomorrow when I get back to the computer. Part of the issue I was having is Composer was NOT seeing the Adobe support files inside /Library/Application Support/Adobe/Lightroom

So, I must be doing something wrong. It seems like the more I look at the same problem, the more elusive the answer is. Doesn't Composer skip certain files/folders and so on? I wonder if the default settings within Composer could be hampering the results?

Thanks Guys!!

Mick

I would recommend NOT repackaging and just using the package as shipped from Adobe. Create a separate package for the licensing/registration. You can then use this same licensing package together with Lightroom 4.0, 4.1, 4.2, 4.3, 4.4, etc...

+1

@gregneagle wrote:

I would recommend NOT repackaging and just using the package as shipped from Adobe. Create a separate package for the licensing/registration. You can then use this same licensing package together with Lightroom 4.0, 4.1, 4.2, 4.3, 4.4, etc...

Interestingly, what I found is the system wide library did not cascade the appropriate rights through additional or new folders that were found during the discovery period of the snapshot of Composer. Once I changed the permissions to match what they SHOULD be, then all worked well.

My guess is, the Adobe support folder in the library folder was not given the proper permissions, therefore it was moved to the user folder instead. Strange behavior, but tested on both Snow and Lion and this certainly fixed it.

Mick

@mconners We ran a test on a Lion machine and confirmed your findings, that on first launch Lightroom creates the folder (prompting the user to authenticate), and the folder belongs to that user. [color=red]Hmmm...BAD ADOBE!!![/color]

$ ls -l /Library/Application Support/Adobe/ | grep Lightroom
drwxr-xr-x   4 donmontalvo  admin   136 Jul 11 12:28 Lightroom

If we put the Lightroom license file in that folder and make sure the file and the parent folder are owned by root:wheel, it works fine:

$ ls -l /Library/Application Support/Adobe/ | grep Lightroom
drwxr-xr-x   4 root         wheel   136 Jul 11 12:28 Lightroom
$

$ ls -l /Library/Application Support/Adobe/Lightroom/ | grep Lightroom 3.0 Registration 
-rw-r--r--  1 root  wheel  407 Jun 27 15:12 Lightroom 3.0 Registration
$

Then as each user launches Lightroom, the files/folders that are created are put in the User domain level:

$ ls -l ~/Library/Application Support/Adobe/Lightroom/
total 0
drwxr-xr-x  3 donmontalvo  admin  102 Jul 11 12:28 Develop Presets
drwxr-xr-x  3 donmontalvo  admin  102 Jul 11 12:28 Export Presets
drwxr-xr-x  2 donmontalvo  admin   68 Jul 11 12:28 External Editor Presets
drwxr-xr-x  2 donmontalvo  admin   68 Jul 11 12:28 Filter Presets
drwxr-xr-x  2 donmontalvo  admin   68 Jul 11 12:28 Keyword Sets
drwxr-xr-x  2 donmontalvo  admin   68 Jul 11 12:28 Label Sets
drwxr-xr-x  2 donmontalvo  admin   68 Jul 11 12:28 Metadata Presets
$

Sending Jody (Adobe) a link to this thread, hoping he can pass this along to whoever is responsible for the Adobe Lightroom installer.

Don