On Fri, Jun 26, 2009 at 10:00 AM, Allan Marcus<al...@lanl.gov> wrote:
>
> No, probably not. I was just being lazy and didn't want to push out
> two packages.
>
> Given that Facter and Puppet are different code branches that are not
> dependent on each other (true?), then having seperate packages seems
> fine.
>
> BTW, are you going to post a new Facter package with the latest version?
thanks for reminding me :)
I'll get one up today.
Please note that for both Puppet and Facter, you can create packages
from any git checkout/source tarball with conf/osx/createpackage.sh
>
> ---
> Thanks,
>
> Allan Marcus
> 505-667-5666
>
>
>
> On Jun 26, 2009, at 10:14 AM, Nigel Kersten wrote:
>
>>
>> On Fri, Jun 26, 2009 at 9:07 AM, Allan Marcus<al...@lanl.gov> wrote:
>>>
>>> I just found the check box in Package Maker to follow symlinks. You
>>> have to double click on each package to get at that preference. I
>>> don't understand why it's not in the Configuration screen.
>>>
>>> At any rate, my meta installer is now working. Thanks for the help.
>>
>> Do you think it's worth me creating a meta-installer for Puppet +
>> Facter for distribution?
>>
>>>
>>> BTW, I've started using Deep Freeze to restore a system to a pristine
>>> state in my test environment. It's awesome; just reboot and your
>>> computer is back to where it was when you "froze" the state. They
>>> have
>>> it for Windowz too. Very mush worth the money.
>>>
>>> ---
>>> Thanks,
>>>
>>> Allan Marcus
>>> 505-667-5666
>>>
>>>
>>>
>>> On Jun 26, 2009, at 9:32 AM, Nigel Kersten wrote:
>>>
>>>>
>>>> On Fri, Jun 26, 2009 at 7:18 AM, Jason Hueske<schwi...@gmail.com>
>>>> wrote:
>>>>>
>>>>> One culprit that I've seen repeatedly is the set of drivers for
>>>>> Sierra
>>>>> Wireless Aircards, if that helps. Leopard and Tiger do indeed keep
>>>>> ruby in separate locations and some installers don't honor that
>>>>> difference correctly when they bundle it.
>>>>
>>>> * shakes fist at Sierra drivers.
>>>>
>>>> So they don't have to be treated as separate locations.
>>>>
>>>> on Tiger, /usr/lib/ruby, /usr/lib/ruby/site_ruby are both
>>>> directories.
>>>>
>>>> On Leopard, they're symlinks.
>>>>
>>>> So long as packages are set to follow symlinks and not overwrite
>>>> them,
>>>> it's safe to install to the symlink location.
>>>>
>>>> Unfortunately due to limitations in the pkg format, it's difficult
>>>> to
>>>> produce an easily auditable package that installs to different
>>>> locations based upon the target OS. I'd have to create an mpkg with
>>>> different packages for Leopard and Tiger, and I resent having to put
>>>> in that work due to other people's broken packages :)
>>>>
>>>> Allan, the setting you want is:
>>>>
>>>> <key>IFPkgFlagFollowLinks</key>
>>>> <true/>
>>>>
>>>> If a metapackage IFPkgFlagFollowLinks setting overrides that of
>>>> child
>>>> pkgs, I'd be tempted to report that as a bug to Apple, as it's
>>>> kind of
>>>> shitty behavior.
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>> Jason
>>>>>
>>>>>
>>>>> On Jun 25, 2009, at 7:52 PM, Nigel Kersten wrote:
>>>>>
>>>>>>
>>>>>> On Thu, Jun 25, 2009 at 5:18 PM, Allan Marcus<al...@lanl.gov>
>>>>>> wrote:
>>>>>>>
>>>>>>> ruby -I /usr/lib/ruby/site_ruby/1.8 puppetd
>>>>>>>
>>>>>>> works! Now why would that work? Do I need to set RUBYLIB when
>>>>>>> using
>>>>>>> the installer packages?
>>>>>>
>>>>>> Are you sure you're not doing something weird with your Ruby
>>>>>> install?
>>>>>>
>>>>>> On Leopard, do you have the default symlinks still?
>>>>>>
>>>>>> /usr/lib/ruby ->
>>>>>> ../../System/Library/Frameworks/Ruby.framework/Versions/Current/
>>>>>> usr/
>>>>>> lib/ruby
>>>>>>
>>>>>> /usr/lib/ruby/site_ruby ->
>>>>>> ../../../../../../../../../../Library/Ruby/Site
>>>>>>
>>>>>> There are packages out there that incorrectly fail to follow
>>>>>> symlinks
>>>>>> for these directories, and break Ruby in lots of ways under
>>>>>> Leopard.
>>>>>> Older bundled packages of RubyCocoa are a prime culprit.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> ---
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Allan Marcus
>>>>>>> 505-667-5666
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Jun 25, 2009, at 5:59 PM, Allan Marcus wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Jun 25, 2009, at 5:43 PM, Nigel Kersten wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, Jun 25, 2009 at 3:03 PM, Allan Marcus<al...@lanl.gov>
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Actually, I tried it on a fresh Tiger build and I get the same
>>>>>>>>>> results :-(
>>>>>>>>>
>>>>>>>>> You're definitely running /usr/bin/puppetd and /usr/bin/
>>>>>>>>> facter ?
>>>>>>>>
>>>>>>>> Yes. confirmed with 'which'
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Do /usr/lib/ruby/site_ruby/1.8/{facter,puppet} exist ?
>>>>>>>>
>>>>>>>> yes
>>>>>>>>
>>>>>>>>
>>>>>>>> this is on a freshly installed updated leopard machine. Install
>>>>>>>> leopard. Run SW Update. Install factor. install puppet. run
>>>>>>>> puppet.
>>>>>>>> fail :-(
>>>>>>>>
>>>>>>>> I did notice the installer for factor is for 1.5.4, which I
>>>>>>>> don't
>>>>>>>> think is the current version. Is there a more recent Mac
>>>>>>>> installer
>>>>>>>> for
>>>>>>>> factor? Could this be the issue? I got the installers from
>>>>>>>>
>>>>>>>> https://sites.google.com/a/explanatorygap.net/puppet/
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> I just installed them on a fresh Tiger install the other day
>>>>>>>>> with
>>>>>>>>> no
>>>>>>>>> problems....
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Any ideas?
>>>>>>>>>>
>>>>>>>>>> ---
>>>>>>>>>> Thanks,
>>>>>>>>>>
>>>>>>>>>> Allan Marcus
>>>>>>>>>> 505-667-5666
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Jun 25, 2009, at 3:54 PM, Allan Marcus wrote:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> hello,
>>>>>>>>>>>
>>>>>>>>>>> I installed facter and puppet from MacPorts and they seemed
>>>>>>>>>>> to
>>>>>>>>>>> work
>>>>>>>>>>> just fine. Since I will be deploying from the packages at
>>>>>>>>>>>
>>>>>>>>>>> So, I uninstalled from MacPorts and installed from the
>>>>>>>>>>> packages.
>>>>>>>>>>> If I
>>>>>>>>>>> try to run facter or puppetd I get errors. Any ideas?
>>>>>>>>>>>
>>>>>>>>>>> bash-3.2# facter
>>>>>>>>>>> /usr/bin/facter:50:in `require': no such file to load --
>>>>>>>>>>> facter
>>>>>>>>>>> (LoadError)
>>>>>>>>>>> from /usr/bin/facter:50
>>>>>>>>>>>
>>>>>>>>>>> bash-3.2# puppetd
>>>>>>>>>>> /usr/bin/puppetd:164:in `require': no such file to load --
>>>>>>>>>>> puppet
>>>>>>>>>>> (LoadError)
>>>>>>>>>>> from /usr/bin/puppetd:164
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ---
>>>>>>>>>>> Thanks,
>>>>>>>>>>>
>>>>>>>>>>> Allan Marcus
>>>>>>>>>>> 505-667-5666
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Nigel Kersten
>>>>>>>>> nig...@google.com
>>>>>>>>> System Administrator
>>>>>>>>> Google, Inc.
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Nigel Kersten
>>>>>> nig...@google.com
>>>>>> System Administrator
>>>>>> Google, Inc.
>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Nigel Kersten
>>>> nig...@google.com
>>>> System Administrator
>>>> Google, Inc.
>>>>
>>>>>
>>>
>>>
>>>>
>>>
>>
>>
>>
>> --
>> Nigel Kersten
>> nig...@google.com
>> System Administrator
>> Google, Inc.
>>
>> >
>
>
> >
>
--
Nigel Kersten
nig...@google.com
System Administrator
Google, Inc.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
