package provider for FreeBSD

[Gregory Orange]

Hi again,
From examples I have gleaned the following snippet for manifests/site.pp

Package { provider => $operatingsystem ? {
FreeBSD => freebsd,
#FreeBSD => ports,
debian => aptitude,
redhat => up2date }}

Are there providers documented somewhere? I'm not sure where to look,
and I haven't come across it in my stumbling, googling, mailing list
lurking or docs.puppetlabs.com.

Importantly, what is the exact behaviour of FreeBSD => freebsd versus =>
ports? I can see that => ports uses /usr/ports (which I can NFS mount
for management gains), and => freebsd uses a specified host (or defaults
to freebsd.org), but I'd really like to see the doco, or at least
someone's overview understanding. Can any of you help me?

Cheers,
Greg.

[R. Tyler Croy]

On Thu, 28 Jun 2012, Gregory Orange wrote:

> Hi again,
> From examples I have gleaned the following snippet for manifests/site.pp
>
> Package { provider => $operatingsystem ? {
> FreeBSD => freebsd,
> #FreeBSD => ports,
> debian => aptitude,
> redhat => up2date }}
>
> Are there providers documented somewhere? I'm not sure where to
> look, and I haven't come across it in my stumbling, googling,
> mailing list lurking or docs.puppetlabs.com.

The different package resource providers and their differences documented here:
<http://docs.puppetlabs.com/references/latest/type.html#package>


- R. Tyler Croy
--------------------------------------
Code: http://github.com/rtyler
Chatter: http://twitter.com/agentdero
rty...@jabber.org

[Gregory Orange]

On 29/06/12 02:18, R. Tyler Croy wrote:
> On Thu, 28 Jun 2012, Gregory Orange wrote:
>> Are there providers documented somewhere? I'm not sure where to
>

> The different package resource providers and their differences documented here:
> <http://docs.puppetlabs.com/references/latest/type.html#package>

Great, thank you. I've settled upon portupgrade as the best provider,
since I can use it to build from the NFS mounted /usr/ports tree. Now I
am experiencing a quirk when a package is to be newly installed:

'ensure => installed' or 'ensure => present' results in the package
being installed as expected.
http://pastebin.com/sdH8F7p1

'ensure => latest' yields no change. For the sample package net/rsync:
http://pastebin.com/HsEaGDRa

The key difference being on line 4 of the paste:
installed: portinstall
latest: pkg_info

pkg_info is _not_ going to install the packages!

Can anyone help me with this?

Cheers,
Greg.

[Gregory Orange]

On 29/06/12 14:38, Gregory Orange wrote:
> I've settled upon portupgrade as the best provider,
> since I can use it to build from the NFS mounted /usr/ports tree. Now I
> am experiencing a quirk when a package is to be newly installed:
>
> 'ensure => installed' or 'ensure => present' results in the package
> being installed as expected.
> http://pastebin.com/sdH8F7p1
>
> 'ensure => latest' yields no change. For the sample package net/rsync:
> http://pastebin.com/HsEaGDRa
>
> The key difference being on line 4 of the paste:
> installed: portinstall
> latest: pkg_info
>
> pkg_info is _not_ going to install the packages!

Assistance on the IRC channel and references to two bugs indicate that
ensure => latest doesn't work on FreeBSD. So I'll investigate some sort
of uninstall->reinstall process when I want to push out upgrades.

http://projects.puppetlabs.com/issues/show/14845
http://projects.puppetlabs.com/issues/show/5951