facterCross-platform library for retrieving facts from OS
3.14.24_9sysutilsΣ=6 3.14.24_9Version of this port present on the latest quarterly branch.
BROKEN: fails to build with Boost>=1.87 DEPRECATED: Reached EOL This port expired on: 2025-05-09 IGNORE: is marked as broken: fails to build with Boost>=1.87
Facter is Puppet's cross-platform system profiling library.
It discovers and reports per-node facts, which are
available in your Puppet manifests as variables.
===> The following configuration options are available for facter-3.14.24_9:
FACTER_JAVA=on: Build with Java bindings for puppetserver
===> Use 'make config' to modify these settings
sysutils/facter: mark as BROKEN with Boost>=1.87 (+)
Since 1.87 release some long-time-ago deprecated Boost.asio facilities was
dropped off
Sponsored by: Future Crew, LLC
Mk/**java.mk: Convert bsd.java.mk to USES
The following features have been added or changed:
- Instead of USE_JAVA use USES=java. This defaults to
USES=java:build,run if NO_BUILD is undefined. Else it defaults to
USES=java:run
- Instead of USE_ANT=yes use USES=java:ant which also implies
USES=java:build
- Instead of JAVA_BUILD=yes use USES=java:build. Does not imply run or
extract
- Instead of JAVA_EXTRACT=yes use USES=java:extract does not imply
build or run
- Instead of JAVA_RUN=yes use USES=java:run does not imply extract or
build
- Instead of USE_JAVA=<version> use USES=java and JAVA_VERSION=<version>
Approved by: mat (portmgr), glewis
Differential Revision: https://reviews.freebsd.org/D48201
sysutils/facter: support openjdk11 and up
Adjusted the patch from the issue to target jdk 8 instead of 7.
Target 8 is supported by all current openjdk version in ports.
PR: 237990
Tested by: poudriere
Approved by: maintainer timeout
Mk/**ruby.mk: Switch from USE_RUBY=yes to USES=ruby
Switch from Mk/bsd.ruby.mk to Mk/Uses/ruby.mk
Notable changes are.
- Mk/bsd.ruby.mk is moved to Mk/Uses/ruby.mk.
- USE_RUBY=yes is replaced with USES=ruby.
- USE_RUBY_EXTCONF is replaced with USES=ruby:extconf.
- USE_RUBY_RDOC is replaced with USES=ruby:rdoc.
- USE_RUBY_SETUP is replaces with USES=ruby:setup.
- RUBY_NO_BUILD_DEPENDS and RUBY_NO_RUN_DEPENDS are replaced with
USES=ruby:{build,none,run}.
- RUBY_REQUIRE isn't used anywhere, so removed.
- USES=gem now implies USES=ruby.
This is mainly the work of yasu@ at https://reviews.freebsd.org/D27863
I have just made some cosmetic changes and ran exp-run to test that the
tree is not in a BROKEN state.
Approved by: portmgr
Differential Revision: https://reviews.freebsd.org/D37925
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
Fix CONFLICTS entries of multiple ports
There have been lots of missing CONFLICTS_INSTALL entries, either
because conflicting ports were added without updating existing ports,
due to name changes of generated packages, due to mis-understanding
the format and semantics of the conflicts entries, or just due to
typoes in package names.
This patch is the result of a comparison of all files contained in
the official packages with each other. This comparison was based on
packages built with default options and may therefore have missed
further conflicts with optionally installed files.
Where possible, version numbers in conflicts entries have been
generalized, some times taking advantage of the fact that a port
(Only the first 15 lines of the commit message are shown above )
devel/yaml-cpp: Update to 0.7.0
- Patch cmake include to actually work
- Bump PORTREVISION on consumers, testing shows it is not completely
binary compatible
- Update yaml-cpp to 0.6.3
- Removed TEST option since it fails to build. Disable tests
unconditionally.
- Bump PORTREVISION on dependent ports. I've observed linker errors
on startup due to library changes
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
lib/inc/internal/util/freebsd/geom.hpp needs to include stdexcept to
build on GCC-based architectures.
PR: 235601
Submitted by: Piotr Kubaj
Approved by: portmgr (tier-2 blanket)
Fix build when devel/rapidjson is installed
devel/leatherman include an old version of RapidJSON that is not compatible
with what devel/rapidjson install. Reorder includes so that the version
included with devel/leatherman is found before the one of devel/rapidjson
because it is what is wanted.
While here, fix `make test`.
No need to bump PORTREVISION.
PR: 233426
Reported by: vladislav.movchan@gmail.com
Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
Install the generated .gemspec file
Building the C implementation of facter also produce a .gemspec file. So far,
it was not installed (probably by mistake: since nothing was using it,
everything was fine). Now that we are about to add a consumer of this file as
sysutils/rubygem-puppetserver-ca to the ports tree, this file must be
installed.
With hat: puppet
Bump PORTREVISION for ports depending on the canonical version of GCC
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.
This includes ports
- featuring USE_GCC=yes or USE_GCC=any,
- featuring USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and those
- with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.
PR: 222542
Update to 3.9.2
- This version does not build with ninja, so disable it for now;
- Remove unneeded patch;
- While here, silent down post-patch operations.
With hat: puppet
sysutils/facter: Drop slave port, add Java option default
Here we drop support for the slave port, since it never quite worked as
desired, nor was it ever submitted, and removes the conditionals to support it.
Also, we add a new default option FACTER_JAVA to build support for Java and
install facter.jar to be used by sysutils/puppetserver5.
Approved by: swills(mentor)
Differential Revision: D12498
Bump PORTREVISION for ports depending on the canonical version of GCC
(via Mk/bsd.default-versions.mk and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++11-lang,
c++14-lang, c++0x, c11, or gcc-c++11-lib.
PR: 219275
Update to 3.8.0
Remove a bunch of patches merged upstream.
Add some new patches to use paths that better fit FreeBSD:
Configuration -> /usr/local/etc/facter/facter.conf
Custom facts -> /usr/local/etc/facter/facts.d/
Cached facts -> /var/facter/cache/cached_facts/
Update to 3.7.1
- Prepare the port to have a slave-port: java-facter;
- Add a bunch of patches that where merged upstream but not yet released so
that facter can be a drop-in replacement of rubygem-facter.
With hat: puppet
Pass maintainership to puppet@
puppet@ is basically aliased to the previous maintainers in order to ease-up
updating Puppet-related ports. The changes where approved by e-mail.
Mark some ports failing on power64. In cases where the error message
was a stub, provide a real one.
While here, pet portlint.
Approved by: portmgr (tier-2 blanket)
Reported by: swills
Bump PORTREVISIONs for ports depending on the canonical version of GCC and
lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using using Mk/bsd.octave.mk which in turn has USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang,
c++11-lang, c++0x, c11, or gcc-c++11-lib.
PR: 216707
sysutils/facter: unbreak build with boost 1.62
vendor/leatherman/logging/src/logging.cc:75:44: error: no matching constructor
for initialization of 'sink_t' (aka
'synchronous_sink<leatherman::logging::color_writer>')
boost::shared_ptr<sink_t> sink(new sink_t(&dst));
^ ~~~~
/usr/local/include/boost/log/sinks/sync_frontend.hpp:72:7: note: candidate
constructor (the implicit copy constructor) not viable: no known conversion from
'ostream *' (aka 'basic_ostream<char> *') to 'const
boost::log::v2_mt_posix::sinks::synchronous_sink<leatherman::logging::color_writer>'
for 1st argument
class synchronous_sink :
^
/usr/local/include/boost/log/sinks/sync_frontend.hpp:123:14: note: candidate
constructor not viable: no known conversion from 'ostream *' (aka
'basic_ostream<char> *') to 'const shared_ptr<sink_backend_type>' for 1st
argument
explicit synchronous_sink(shared_ptr< sink_backend_type > const& backend) :
^
/usr/local/include/boost/log/sinks/sync_frontend.hpp:134:45: note: candidate
template ignored: substitution failure [with T0 = std::__1::basic_ostream<char,
std::__1::char_traits<char> > *]: no type named 'type' in
'boost::log::v2_mt_posix::aux::enable_if_named_parameters<std::__1::basic_ostream<char,
std::__1::char_traits<char> > *, boost::log::v2_mt_posix::aux::sfinae_dummy>'
BOOST_LOG_PARAMETRIZED_CONSTRUCTORS_GEN(BOOST_LOG_SINK_CTOR_FORWARD_INTERNAL, ~)
^
/usr/local/include/boost/log/detail/parameter_tools.hpp:44:66: note: expanded
from macro 'BOOST_LOG_PARAMETRIZED_CONSTRUCTORS_GEN'
(Only the first 15 lines of the commit message are shown above )
- Update devel/yaml-cpp to 0.5.3
- Project moved to GITHUB
- LICENSE_FILE renamed
- Regenerated patch
- Bumped PORTREVISION in dependent ports due to ABI changes.
Number of commits found: 126 (showing only 100 on this page)
