keeleysam / instadmg

Automatically exported from code.google.com/p/instadmg
0 stars 0 forks source link

Symlinks Respected? /usr/lib/ruby/site_ruby Symlink not followed. #34

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Download most current version of InstaDMG (1.6b2)
2.  Used 10.6 base image
3.  Dropped 10.6.2 combo package into build train
4.  Load Facter/Puppet packages from 
https://sites.google.com/a/explanatorygap.net/puppet/ (facter 1.5.7 and 
puppet 25.4) into build train.
5.  Loaded 3 more packages - an ARD metapackage to enable ARD with all 
users and create a specific ARD user, a Packagemaker package to install 
our puppet-calling script in /usr/bin, and another package to install and 
load a launchdaemon to call the puppet script in /usr/bin.
6.  Baked the image and deployed out to clients.  
7.  When clients loaded the image, the folder /usr/lib/ruby/site_ruby was a 
folder, and not a symlink to "../../../../../../../../../../Library/Ruby/Site" 
- 
which caused puppet and facter to fail.

What is the expected output? What do you see instead?
/usr/lib/ruby/site_ruby needs to symlink to the folder named above, and 
packages need to be installed respecting the symlinks.  I tried a regular 
Snow Leopard client with 10.6.2 installed, and then tried installing all of 
the above packages one by one - none of them screw up the symlink

What version of InstaDMG are you running? What revision number (this 
should
be the second line of your package log)?
1.6b2 revision 261

What OS are you running on (booted from)?
Created the DMG from a 10.6.2 machine

What OS are you installing?
DMG uses 10.6 and the 10.6.2 combo updater.

Please provide any additional information below.
This actually worked fine in 10.5 with InstaDMG 1.5 Revision 202.  I may 
try playing with that again (though I don't believe that revision likes 10.6).  
Feel free to email me for any clarification - glarizza@me.com or Twitter - 
glarizza

Original issue reported on code.google.com by ccsh...@gmail.com on 11 Mar 2010 at 12:52

GoogleCodeExporter commented 9 years ago
Please Close this issue - it turns out that the Puppet package isn't respecting 
symlinks 
when installing on a non-boot volume.  

Original comment by ccsh...@gmail.com on 11 Mar 2010 at 6:28

Attachments:

GoogleCodeExporter commented 9 years ago
Thanks for the update, I was just baking an image to confirm that this was not 
a problem on the vanilla image.

Original comment by kuehn.k...@gmail.com on 11 Mar 2010 at 6:33