Hey Roy, The Luggage recipe ( https://github.com/unixorn/luggage-examples/tree/master/puppet) is out-of-band from our package creation processes (and, in fact, is something I created at my old job to work with my workflow THERE, so it shouldn't be considered authoritative by any means), so that's not something we're willing to provide.
As for the createpackage.sh script, I'll check with folks internally and try to get you an answer. Thanks for letting us know about the problem! On Fri, Mar 15, 2013 at 10:48 AM, Roy Nielsen <[email protected]> wrote: > Maybe the createpackage.sh script should be removed (or fixed). > > I'd prefer you keep it (and fix it), unless you have a luggage recipe with > the rake command.. > > What do you think? > > Thank you for the instructions. > > Regards, > -Roy > > > On Fri, Mar 15, 2013 at 11:07 AM, Matthaus Owens > <[email protected]>wrote: > >> Roy, >> Mac packages for puppet and facter can currently be created with our >> packaging rake tasks. >> rake package:bootstrap >> followed by >> rake package:apple >> will generate a dmg in the pkg directory. The rake task is >> functionally similar to the createpackage.sh build script. >> >> On Fri, Mar 15, 2013 at 9:21 AM, Andy Parker <[email protected]> wrote: >> > Haus, how have we been building our OSX packages? >> > >> > On Fri, Mar 15, 2013 at 8:33 AM, Roy Nielsen <[email protected]> wrote: >> >> Hello, >> >> >> >> Just an FYI, the Mac createpackage.sh build script in the >> puppet-2.7.21 & >> >> facter-1.6.18 tarballs are both broken. >> >> >> >> The script references conf/osx/PackageInfo.plist and >> conf/osx/preflight, and >> >> those don't exist any more. >> >> >> >> They're now in: >> >> >> >> ext/osx/PackageInfo.plist >> >> ext/osx/preflight >> >> >> >> Anyone that automated the download and build of the Mac packages with >> >> luggage now have to build the packages by hand. >> >> >> >> Regards, >> >> -Roy >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> Groups >> >> "Puppet Developers" group. >> >> To unsubscribe from this group and stop receiving emails from it, send >> an >> >> email to [email protected]. >> >> To post to this group, send email to [email protected]. >> >> Visit this group at http://groups.google.com/group/puppet-dev?hl=en. >> >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >> >> >> >> >> -- >> Matthaus Owens >> Release Manager, Puppet Labs >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/puppet-dev?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/puppet-dev?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Gary Larizza Professional Services Engineer -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
