Closing the loop on this: We completed the cutover. facter/master is now
native facter, and the cfacter repository is closed
On Fri, Mar 20, 2015 at 11:16 AM, Michael Smith <
michael.sm...@puppetlabs.com> wrote:
> As a heads up, we plan to merge https://github.com/puppetlabs/cfacter to
> https://
As a heads up, we plan to merge https://github.com/puppetlabs/cfacter to
https://github.com/puppetlabs/facter/tree/master (facter/master) this
afternoon. If you're pinning against facter/master, you may want to change
that to facter/2.x unless you're prepared to compile the native binary.
Specific
"probably"
The code is written to standard operating system APIs, and we are very
aggressive with our compiler warnings (which helps avoid
undefined/architecture-specific behavior). I would expect it to work, but
as always with C++ sometimes things get weird.
Depending on the architecture* we wou
On Thu, Mar 5, 2015 at 1:25 PM, Roy Nielsen wrote:
> Curious - will this be able to be compiled and used on Arm or other
> architectures (cross platform compatibility)?
>
>
> I have been toying with ARM chips at home to get this working. (Not
official from Puppet Labs). Thus far I haven't got it
Curious - will this be able to be compiled and used on Arm or other
architectures (cross platform compatibility)?
Thank you,
-Roy
On Wed, Mar 4, 2015 at 4:45 PM, Kylo Ginsberg wrote:
> As some of you know, we have been working on a native reimplementation of
> facter in C++11 in the https://git
As some of you know, we have been working on a native reimplementation of
facter in C++11 in the https://github.com/puppetlabs/cfacter project. At
the same time, we've been continuing to add features and fixes in parallel
in the ruby facter project at good ol' https://github.com/puppetlabs/facter.
