Thanks, all. I was originally hoping to just be able to build ports the old
fashioned way, but have abandoned that route. I've upgraded to pkgng and am
successfully using the zleslie/pkgng provider. Things are going well and
I'm already very excited at how easy it's going to be to setup new
On 12/19/2013 04:44 PM, Patrick Gibson wrote:
Thanks, all. I was originally hoping to just be able to build ports the old
fashioned way, but have abandoned that route. I've upgraded to pkgng and am
successfully using the zleslie/pkgng provider. Things are going well and
I'm already very
Just wanted to throw in that you should update to pkgng. pkg_add isnt even
going to be an option in FreeBSD10. I have been using
https://forge.puppetlabs.com/zleslie/pkgng successfully with FreeBSD10 Beta 3
and puppet.
--
You received this message because you are subscribed to the Google
I'm a first-time Puppet user, working with FreeBSD 9.2, Puppet 3.3.1, and
Ruby 2.0. I'm starting out with a very simple setup to test the waters:
node 'myhost' {
package { 'devel/jsmin':
ensure = 'installed',
provider = 'ports'
}
}
When I run:
puppet apply -v --debug
First, to clarify - do you have pkgng installed on your FreeBSD box?
That is, should you be using /usr/sbin/pkg instead of
/usr/local/bin/pkg_info if you are doing local package management?
If so, the current freebsd provider is not likely to work well for you,
as it's pretty tied into the
On 12/17/2013 04:31 PM, Patrick Gibson wrote:
Debug: Executing '/usr/local/sbin/portupgrade -N -M BATCH=yes devel/jsmin'
In short, out-of-the-box, puppet is broken on FreeBSD in regards to package
handling.
Portupgrade doesn't like being run with stdin not being a terminal. You'll
probably find
