Announce: Facter 2.0.0rc4 Available

[Moses Mendoza]

Facter 2.0.0rc4 is a maintenance release candidate with bug fixes.

It includes contributions from Josh Cooper, Jeff Weiss, Stefan Schulte, and Moses Mendoza.

This release is available for download at:
 https://downloads.puppetlabs.com/facter/facter-2.0.0rc4.tar.gz

 https://apt.puppetlabs.com

 https://yum.puppetlabs.com

See the Verifying Puppet Download section at:
 http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet#Verifying+Puppet+Downloads

Please report feedback via the Puppet Labs Redmine site, using an
affected version of 2.0.0rc4:
 http://projects.puppetlabs.com/projects/facter/

Full Release Notes at: https://projects.puppetlabs.com/projects/facter/wiki/Wiki

Facter 2.0.0rc4 Highlights
======================

(#10261) Detect x64 architecture on Windows

    

    Previously, the hardwaremodel fact was using

    

        RbConfig::CONFIG['host_cpu']

    

    for Windows, but this returns i686 on a 64-bit OS, which is incorrect. And

    this caused the architecture fact to be reported as i386, which is also

    wrong.

    

    This commit updates the hardwaremodel fact on Windows to return the

    appropriate cpu model, e.g. x64, i686, etc. Based on that, the

    architecture fact will either be x86 or x64, and can be used to install

    architecture-specific packages, e.g. splunk-4.2.4-110225-x64-release.msi.

(#13678) Allow passing shell built-ins to exec method on windows

    

    The former exec method tried to run the command on windows no matter

    wether it could be found on the filesystem or not. This allowed end

    users to run shell-builtins with the exec method.

    

    The new exec method always tried to expand the binary first and returned

    nil if the binary was not found. This commit now restores the old

    behaviour on windows: Even if we fail to expand the command, we will try

    to run the command in the exact same way as it was passed to the exec

    method in case it is indeed a shell built-in. But we will now raise a

    deprecation warning.

    

    Reason for deprecating this "even if we cannot find it, just run it"

    behaviour: We may want to predetermine the paths where facter tries to find

    binaries in the future. A fall back behaviour may then lead to strange

    results. Most built-ins can be expressed in pure ruby anyways.

(#13678) Join PATHs correctly on windows

    

    On windows File.join joins with the File::SEPARATOR which is '/' on

    windows. While a lot of the windows API and the ruby filetests allow

    / as a separator we should use File::ALT_SEPARATOR ('\' on windows) to

    create pathnames on windows

Facter 2.0.0rc4 Changelog
===================

Josh Cooper (4)

    f42896d (#14764) Stub architecture fact when Windows facts run on Linux

    964d1f0 (#12864) Close registry key

    ab025bb Revert "Revert "(#12864) Windows: get primary DNS from registry""

    478386d (#10261) Detect x64 architecture on Windows

Jeff Weiss (1)

    f44ca52 (maint) Fix hardware model fact for ruby 1.9

Stefan Schulte (12)

    2043244 (#13678) Remove deprecation msg triggerd by the ipaddress6 fact 
    d118d81 (#13678) Add filename extension on absolute paths on windows
    85654b0 (#13678) Allow passing shell built-ins to exec method on windows
    8f4c016 (#13678) Single quote paths on unix with spaces
    2d164e8 (#13678) Join PATHs correctly on windows
    e7e7e8f (#13678) Extend spec tests for expand_command
    0fea7b0 maint: Add shared context for specs to imitate windows or posix
    60d0cd2 (#13678) Fix spec failures on windows
    121a2ab (#13678) Fix quoting in expand_command
    55b1125 (#13678) Add more unit tests for new methods
    9086c0a (#13678) Add RDoc documentation for new methods

    165ace4 (#13678) Convert command to absolute paths before executing

Moses Mendoza (1)

    d6a3e91 Make package task depend on tar in Rakefile