| 1 | # $Id: Portfile,v 1.1 2003/07/07 05:16:10 rshaw Exp $ |
|---|
| 2 | PortSystem 1.0 |
|---|
| 3 | name cfengine |
|---|
| 4 | version 2.0.7p3 |
|---|
| 5 | categories sysutils |
|---|
| 6 | maintainers robert@or.homeip.net |
|---|
| 7 | description a tool for setting up and maintaining computer systems |
|---|
| 8 | master_sites ftp://ftp.iu.hio.no/pub/cfengine/ \ |
|---|
| 9 | http://sunsite.utk.edu/ftp/pub/cfengine/cfengine-ftp/ \ |
|---|
| 10 | ftp://ftp.cfengine.webmotion.net/pub/cfengine/ |
|---|
| 11 | checksums md5 f21b3775ad2a5288ac8f794a9f36f168 |
|---|
| 12 | depends_lib lib:libdb:db4 |
|---|
| 13 | patch { |
|---|
| 14 | cd ${worksrcpath} |
|---|
| 15 | reinplace "s%/usr/local%/opt/local%g" configure |
|---|
| 16 | reinplace "s%BERKELEY_DB_LIB=\"-l\$v\"%if \[ \"x\$v\" == \"xdb4\" ]; then BERKELEY_DB_LIB=\"-ldb-4\"; else &; fi%" configure |
|---|
| 17 | } |
|---|
| 18 | configure.args --with-berkeleydb=yes |
|---|
| 19 | |
|---|
| 20 | long_description \ |
|---|
| 21 | Cfengine, or the configuration engine is an autonomous agent and a \ |
|---|
| 22 | middle to high level policy language for building expert systems which \ |
|---|
| 23 | administrate and configure large computer networks. Cfengine uses the \ |
|---|
| 24 | idea of classes and a primitive intelligence to define and automate the \ |
|---|
| 25 | configuration and maintenance of system state, for small to huge \ |
|---|
| 26 | configurations. Cfengine is designed to be a part of a computer immune \ |
|---|
| 27 | system, and can be thought of as a gaming agent. It is ideal for cluster \ |
|---|
| 28 | management and has been adopted for use all over the world in small and \ |
|---|
| 29 | huge organizations alike. \ |
|---|
| 30 | \ |
|---|
| 31 | The main purpose of cfengine is to allow you to create a single, central \ |
|---|
| 32 | system configuration which will define how every host on your network \ |
|---|
| 33 | should be configured in an intuitive way. An interpreter runs on every \ |
|---|
| 34 | host on your network and parses the master file (or file-set), the \ |
|---|
| 35 | configuration of each host is checked against this file and then, if you \ |
|---|
| 36 | request it, any deviations from the defined configuration are fixed \ |
|---|
| 37 | automatically. You do not have to mention every host specifically by \ |
|---|
| 38 | name in order to configure them: instead you can refer to the properties \ |
|---|
| 39 | which distinguish hosts from one another. Cfengine uses a flexible \ |
|---|
| 40 | system of "classes" which helps you to single out a specific group of \ |
|---|
| 41 | hosts with a single statement. |
|---|
| 42 | |
|---|
