ports/sysutils/rubygem-chef/files, branch 2016Q3

Fix patches mangled with gem 2.6.2 update

2016-04-04T15:37:19Z

Pointyhat to: swills Reported by: antoine

devel/ruby-gems: Update to 2.6.2

2016-04-04T15:24:52Z

PR: 208371 Submitted by: wen (partial)

- Rename gemspec patch to patch-gemspec

2016-04-02T07:15:16Z

With hat: ruby

www/rubygem-rest-client: update to 1.8.0

2015-05-31T20:58:12Z

PR: 200504 Differential Revision: https://reviews.freebsd.org/D2696 Submitted by: Sevan Janiyan Approved by: swills (mentor) Security: CVE-2015-1820 Security: CVE-2015-3448

- Fix gemspec for rubygem-highline 1.7.2 update

2015-05-10T20:17:50Z

- Bump PORTREVISION for package change

- update security/rubygem-net-ssh to 2.2.2,2 [1]

2013-01-08T00:35:19Z

- update devel/rubygem-mixlib-authentication to 1.3.0 [2] - update devel/rubygem-highline to 1.6.15 [3] - update sysutils/rubygem-chef to 10.16.4 [4] PR: 171010 [1] PR: 173646 [2] PR: 173647 [3] PR: 171005 [4] Submitted by: nickdewing@gmail.com [1,4] Submitted by: maintainer, renchap@cocoa-x.com [2,4], renchap@cocoa-x.com [3]

The chef_client init script should set up the pidfile in

2012-03-22T17:53:44Z

/var/run/chef-client.pid and instruct the chef-client process to write its PID to this file when daemonizing. Without a pidfile, the status and onestatus command fall back to process inspection. If chef is run with a resource defined to :stop the chef_client service, such as chef-client::cron, then the non-daemonized chef-client process effectivelly kills itself by running /usr/local/etc/rc.d/chef_client status and /usr/local/etc/rc.d/chef_stop. Run chef-client manually, then run /usr/local/etc/rc.d/chef_client onestatus. The status will report chef-client running with the PID of the manually invoked chef-client process. - Bump PORTREVISION Submitted by: Scott Sanders (private e-mail) Approved by: maintainer (implicit) Feature safe: yes

In the rc.d scripts, change assignments to rcvar to use the

2012-01-14T08:57:23Z

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.

- The %%RC_SUBR%% variable in the rc script source files/chef_client.in isn't getting replaced by default. Rather than adding this variable to SUB_LIST, it makes more sense to explicitly replace it in the source file itself. This is done in numerous other rc script source files as well as in the example in the Porter's Handbook.

2011-03-05T01:48:11Z

- bump PORTREVISION PR: ports/155279 Submitted by: Dimitri Aivaliotis Approved by: maintainer (Renaud Chaput)

Chef is a systems integration framework, built to bring the benefits of

2011-01-18T12:00:11Z

configuration management to your entire infrastructure. With Chef, you can: * Manage your servers by writing code, not by running commands. * Integrate tightly with your applications, databases, LDAP directories, and more. * Easily configure applications that require knowledge about your entire infrastructure ("What systems are running my application?" "What is the current master database server?") WWW: http://wiki.opscode.com/display/chef/Home PR: ports/153504 Submitted by: Renaud Chaput Feature safe: yes