Puppet 3.x

Behrang Saeedzadeh behrangsa at gmail.com
Fri Dec 5 22:14:09 PST 2014

Hi Nigel,

I am trying to update the Portfile for facter to version 2.3.0. So far,
here's the new Portfile:

However running facter then fails with this error:

Error loading fact /opt/local/lib/ruby/site_ruby/1.8/facter/ec2.rb: no such
file to load -- cfpropertylist
Error loading fact /opt/local/lib/ruby/site_ruby/1.8/facter/macosx.rb: no
such file to load -- cfpropertylist
Error loading fact /opt/local/lib/ruby/site_ruby/1.8/facter/processor.rb:
no such file to load -- cfpropertylist
/opt/local/lib/ruby/site_ruby/1.8/facter/processors/os.rb:147:in `require':
no such file to load -- cfpropertylist (LoadError)

Any ideas what is causing this?

Best regards,

On Sun, Oct 26, 2014 at 9:16 PM, Nigel Kersten <nigel at explanatorygap.net>

> On Sun, Oct 26, 2014 at 3:06 AM, Ryan Schmidt <ryandesign at macports.org>
> wrote:
>> On Oct 26, 2014, at 5:01 AM, Nigel Kersten wrote:
>> > I really haven't been maintaining this for years Behrang, which is why
>> I set it to open maintainer and have tried to encourage various people over
>> the years. I should probably just remove myself as I'm not being a
>> maintainer in any useful sense.
>> >
>> > I'm no longer using MacPorts at a large scale, and am somewhat ashamed
>> to say I've jumped ship to Homebrew for my personal Mac software needs,
>> which are pretty minimal these days as I do all my development in Linux
>> vagrant boxes. I'm not a huge fan of Homebrew (did we really need another
>> port system?) but it's what most of my co-workers use, so I'm following the
>> herd.
>> >
>> > I can't imagine it's a very difficult port, but you're the first person
>> to nag about it in a long time, and there obviously isn't a huge pent-up
>> demand.
>> >
>> > The Mac pkgs for Puppet that we distributed at Puppet Labs are pretty
>> good these days, and are my first goto for Puppet on OS X.
>> >
>> > However I'm happy to dredge through my memory and give someone a hand
>> bootstrapping themselves into being the new maintainer and moving this onto
>> Puppet 3.x.
>> The main question I have when a new major version of a software package
>> comes out is: do we update the existing port to that new version, or is
>> there still value in keeping the old version around? From what I gather in
>> the ticket, the old version is deprecated, so we should probably just
>> update the existing port, but I don't use puppet so I don't know for sure;
>> perhaps you can answer this.
> Puppet has been semantically versioned for a while, so this isn't strictly
> speaking a backwards compatible update.
> I don't believe the Port has been following the minor updates regularly,
> so users are probably missing some of the deprecation warnings that they
> should have seen before crossing the boundary to 3.x.
> I don't see much utility in keeping the 2.x series around though. 3.0 was
> released nearly two years ago :/ and there are at least a few security
> patches that I don't believe have been backported to 2.x
>> I can remove you as maintainer of puppet and facter if you'd like; it's
>> probably not optimal to have a maintainer listed who doesn't use MacPorts
>> themselves.
> That would be great Ryan, thanks. I'll stay on the list for a while longer
> to give anyone a hand who wants to take on maintaining, otherwise given how
> out of date it is, it may make sense to drop them entirely.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-users/attachments/20141206/23a458bf/attachment.html>

More information about the macports-users mailing list