The recently imposed "must be logged in" restriction is a response to increased bot traffic on the site. This affects search, commits, and vuxml pages.
Search engines are not blocked. Try using "site:www.freshports.org" and your search terms.
This service is getting updated while this announcement is displayed. Commit processing is paused. Started at 16:21 - expected finish: 19:00 (was 18:00) UTC
Port details
cfengineSystems administration tool for networks
3.28.0sysutilsΣ=18 3.28.0Version of this port present on the latest quarterly branch.
Cfengine is an automated suite of programs for configuring and
maintaining Unix-like computers. It has been used on computing arrays
of between 1 and 20,000 computers since 1993 by a wide range of
organizations. Cfengine is supported by active research and was the
first autonomic, hands-free management system for Unix-like operating
systems. Cfengine is an autonomic maintenance system not merely a
change management roll-out tool. Cfengine has a history of security
and adaptability.
===> The following configuration options are available for cfengine-3.28.0:
LIBVIRT=off: Virtualization support via libvirt
MYSQL=off: MySQL database support
PGSQL=off: PostgreSQL database support
===> Use 'make config' to modify these settings
sysutils/cfengine328: Add new port
Add the latest cfengine to the ports collection.
Update the sysutils/cfengine metaport to point to the new port. It
becomes default.
sysutils/cfengine*: Introduce crengine325 and cfengine-masterfiles325
Add ports for the new cfengine and cfengine-masterfiles 3.25.0.
Make cfengine325 and cfengine-masterfiles325 the default cfengine
ports/packages.
sysutils/cfengine*: Introduce crengine324 and cfengine-masterfiles324
Add ports for the new cfengine and cfengine-masterfiles 3.24.0.
Make cfengine324 and cfengine-masterfiles324 the default cfengine
ports/packages.
sysutils/cfengine322: Introduce cfengine323 and cfengine-masterfiles323
Add ports for the new cfengine and cfengine-masterfiles 3.23.0.
Make cfengine323 and cfengine-masterfiles323 the default cfengine
ports/packages.
sysutils/cfengine322: Introduce cfengine322 and cfengine-masterfiles322
Add ports for the new cfengine and cfengine-masterfiles 3.22.0.
Make cfengine322 and cfengine-masterfiles322 the default cfengine
ports/packages.
sysutils/cfengine321: Introduce cfengine321 and cfengine-masterfiles321
Add ports for the new cfengine and cfengine-masterfiles 3.21.0.
Make cfengine321 and cfengine-masterfiles321 the default cfengine
ports/packages.
sysutils/cfengine*: Add cfengine320 and cfengine-masterfiles320
cfengine 3.20 and cfengine-masterfiles 3.20 are the newest to be
released by the cfengine folks.
Welcome the new cfengine317 and cfengine-masterfiles317. They
become the default cfengine and cfengine-materfiles.
cfengine315 and cfengine-masterfiles are deprected, expriring one
year from today.
Welcome the new cfengine313. While here use the cfengine-devel
pkg-plist as it sorts entries in the correct order. Update the
cfengine meta-port to include 313.
Update cfengine310 and cfengine-masterfiles310 3.10.0 --> 3.10.1.
cfengine310 and cfengine-masterfiles310 are now the default
cfengine and cfengine-masterfiles ports.
Welcome the new cfengine and cfengine-masterfiles 3.10.
Adjust the other cfengine and cfengine-masterfiles ports CONFLICTS to
recognize the new cfengine sister ports.
Add cfengine and cfengine-masterfiles 310 to their respective metaports.
Introduce new ports:
- cfengine39 (3.9.0), copied from cfengine38
- cfengine-masterfiles39 (3.9.0), copied from cfengine-masterfiles38
- add cfengine39 to cfengine metaport (non-default for now)
- add cfengine-masterfiles39 to cfengine-metafiles metaport (not default for
now)
Sort documentation files in cfengine39.
cfengine/Makefile:
- Add CFENGINE_VERSION 35
cfengine-devel/Makefile:
- Mark IGNORE since development has not branched yet
Add cfengine 3.5.0:
New features:
- classes promises now take an optional scope constraint.
- new built-in functions: every, none, some, nth, sublist, uniq, filter
- cf-promises flag --parse-tree is replaced by --policy-output-format=,
requiring the
user to specify the output format (none, cf, json)
- cf-promises allows partial check of policy (without body common
(Only the first 15 lines of the commit message are shown above )
Implement the concept of a "master" port for the set of
sysutils/cfengine* ports.
The idea here is two-fold:
1.) Users should not need to ever change port origins
for a default software version bump;
2.) Users should expect to exist an unversioned port
directory to reflect the latest major version (and
they should be correct in this expectation).
With this change, users can install the sysutils/cfengine
port, and by default track the latest major version of the
software. Subsequent version releases, for example the 3.5
branch, will not require any interaction from user side.
(Only the first 15 lines of the commit message are shown above )
In the rc.d scripts, change assignments to rcvar to use the
literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.
Fix a few "bad example" problems in the rc.d scripts that have been
propogated by copy and paste.
1. Primarily the "empty variable" default assignment, which is mostly
${name}_flags="", but fix a few others as well.
2. Where they are not already documented, add the existence of the _flags
(or other deleted empties) option to the comments, and in some cases add
comments from scratch.
3. Replace things that look like:
prefix=%%PREFIX%%
command=${prefix}/sbin/foo
to just use %%PREFIX%%. In many cases the $prefix variable is only used
once, and in some cases it is not used at all.
4. In a few cases remove ${name}_flags from command_args
5. Remove a long-stale comment about putting the port's rc.d script in
/etc/rc.d (which is no longer necessary).
No PORTREVISION bumps because all of these changes are noops.
Update to 2.2.9.
PR: ports/131040
Submitted by: Eygene Ryabinkin <rea-fbsd at codelabs.ru>
Patch by: Jo Rhett <jrhett at netconsonance.com> (maintainer)
Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
(Only the first 15 lines of the commit message are shown above )
Fixup for previous commit:
- Correct pkg-plist by adding two newly added intermediate
libraries. [1]
- Use better way to make dependency on Berkeley DB. [2]
Pointy hat to: delphij
Reported by: Scot Hetzel <swhetzel gmail com> [1]
tinderbox via pav and edwin [2]
- Update to 2.2.3;
- Make BDB 4.6 as default BDB version;
- Modify MASTER_SITES according to official website.
Submitted by: delphij
PR: ports/118562
Approved by: maintainer timeout
- Set --mandir and --infodir in CONFIGURE_ARGS if the configure script
supports them. This is determined by running ``configure --help'' in
do-configure target and set the shell variable _LATE_CONFIGURE_ARGS
which is then passed to CONFIGURE_ARGS.
- Remove --mandir and --infodir in ports' Makefile where applicable
Few ports use REINPLACE_CMD to achieve the same effect, remove them too.
- Correct some manual pages location from PREFIX/man to MANPREFIX/man
- Define INFO_PATH where necessary
- Document that .info files are installed in a subdirectory relative to
PREFIX/INFO_PATH and slightly change add-plist-info to use INFO_PATH and
subdirectory detection.
PR: ports/111470
Approved by: portmgr
Discussed with: stas (Mk/*), gerald (info related stuffs)
Tested by: pointyhat exp run
- Update to 2.1.22
- Respect users' PTHREEAD related settings
- Correct usage of BerkeleyDB
- Use Berkeley DB 4.4 per original authors
PR: ports/109707
Approved by: maintainer timeout (19 days)
- Patch to fix berkeley db detection in configure script. Fixes compilation
when multiple db ports are installed
- Patch to explicitly link with included libpub.a, instead of one in /usr/local
- Patch to never rebuild documentation, the full copy is included
PR: ports/106790
Submitted by: Nick Barkas <snb@threerings.net>
Approved by: maintainer timeout (sergei; 1 month)
- Resurrect sysutils/cfengine port removed year ago. It is currently
synced with sysutils/cfengine2 which it is going to replace.
The reason for that is Cfengine 2.x being the stable version now,
so the need for keeping both old 1.x (sysutils/cfengine) and the new
2.x (sysutils/cfengine2) has been obsoleted.
This is currently disconnected from the build.
- Remove sysutils/cfengine (cfengine-1.x) - the port is marked DEPRECATED
and has expired on 2005-09-14.
Any cfengine-1.x users should consider migrating to cfengine-2.x
(sysutils/cfengine2).
Approved by: gordon (maintainer)
- Mark this port DEPRECATED; users are advised to use sysutils/cfengine2
- Set EXPIRATION_DATE to 6 months from now
- Set NO_LATEST_LINK
Approved by: gordon (maintainer) on freebsd-ports
Remove conditional dependencies on security/tcp_wrapper: That port
hasn't existed since October 2002, and tcp_wrapper has been included in
the base system since March 1999.
Fix cfengine port now that makeinfo splits info -> html output. This broke
package building. The solution is to force it back to creating a monolithic
html file.
Submitted by: kris
BerkeleyDB cleanup - stage 2
Update databases/db3 to 3.3.11, and fix the few ports that need sorting
after the shlib version update, and a slight API change from 3.2.x->3.3.x
Update URLs for cfengine port to correctly reflect the website and the
authoritative FTP site for cfengine. Also remove the dependence on teTex
while port building since it is fscking huge and ugly. When package
building, add the dependence on teTex so more docs are available in the
package.
PR: 37239
Submitted by: maintainer
First round of auto* cleanups: - USE_AUTO* -> USE_AUTO*_VER=* where required
- USE_AUTO* / *_DEPENDS=.*auto*:*/devel/auto* -> GNU_CONFIGURE where OK -
Other minor changes to fix things
This patch fixes the following problems: * cfengine deadlocking in the
resolver due to being linked against libc_r * cfd issuing 'ioctl: No such
network device' whenever it is invoked.
Per the instructions of the software, cfengine is now dependent on BerkleyDB 3.
In fact, the only thing (that I can tell anyway) that uses the DB functions is
cfd. I'm guessing most people don't use it, especially since I haven't heard
any complaints about it.
Change GNU_CONFIGURE to USE_AUTOCONF. cfengine comes with a configure script
generated with configure 1.12, which has a POSIX-related IFS bug and doesn't
completely work with modern shells.
