Revision bump

(Portage version: 2.2.1/cvs/Linux x86_64, signed Manifest commit with key D628E536)

6 files changed, 365 insertions, 51 deletions

diff --git a/app-admin/tripwire/ChangeLog b/app-admin/tripwire/ChangeLog
index 6f98af120b2f..ac1572185703 100644
--- a/app-admin/tripwire/ChangeLog
+++ b/app-admin/tripwire/ChangeLog
@@ -1,6 +1,14 @@
 # ChangeLog for app-admin/tripwire
 # Copyright 1999-2013 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/app-admin/tripwire/ChangeLog,v 1.51 2013/09/03 15:30:16 nimiux Exp $
+# $Header: /var/cvsroot/gentoo-x86/app-admin/tripwire/ChangeLog,v 1.52 2013/09/25 08:45:54 nimiux Exp $
+
+*tripwire-2.4.2.2-r2 (25 Sep 2013)
+
+  25 Sep 2013; Chema Alonso <nimiux@gentoo.org> +tripwire-2.4.2.2-r2.ebuild,
+  +files/tripwire-2.4.2.2-twpol-GENERIC.patch, +files/tripwire,
+  files/tripwire.txt, metadata.xml:
+  Revision bump. Clean up, update of files and inclusion of new "setup" USE
+  flag. Thanks to Chuck Seyboldt
 
   03 Sep 2013; Chema Alonso <nimiux@gentoo.org> metadata.xml:
   Fix tag for spanish description in metadata.xml. Thanks to Chuck Seyboldt
diff --git a/app-admin/tripwire/files/tripwire b/app-admin/tripwire/files/tripwire
new file mode 100644
index 000000000000..26b5cdb8d6ca
--- /dev/null
+++ b/app-admin/tripwire/files/tripwire
@@ -0,0 +1,10 @@
+#!/bin/sh
+HOST_NAME=`uname -n`
+if [ ! -e /var/lib/tripwire/${HOST_NAME}.twd ] ; then
+	echo "****    Error: Tripwire database for ${HOST_NAME} not found.  ****"
+	echo "**** Check tripwire.txt file for instructions or install      ****"
+	echo "**** app-admin/mktwpol package (if you used the \"setup\"  ****"
+	echo "**** USE flag, this has been done for you already.            ****"
+else
+        test -f /etc/tripwire/tw.cfg &&  /usr/sbin/tripwire --check --quiet
+fi
diff --git a/app-admin/tripwire/files/tripwire-2.4.2.2-twpol-GENERIC.patch b/app-admin/tripwire/files/tripwire-2.4.2.2-twpol-GENERIC.patch
new file mode 100644
index 000000000000..12b2419c5e71
--- /dev/null
+++ b/app-admin/tripwire/files/tripwire-2.4.2.2-twpol-GENERIC.patch
@@ -0,0 +1,25 @@
+--- a/policy/twpol-GENERIC.txt	2011-11-21 11:06:56.000000000 -0500
++++ b/policy/twpol-GENERIC.txt	2013-09-11 08:13:34.000000000 -0400
+@@ -55,14 +55,14 @@
+ ##############################################################################
+ 
+ @@section GLOBAL
+-TWROOT=;
+-TWBIN=;
+-TWPOL=;
+-TWDB=;
+-TWSKEY=;
+-TWLKEY=;
+-TWREPORT=;
+-HOSTNAME=;
++#TWROOT=;
++TWBIN=/usr/sbin;
++TWPOL=/etc/tripwire;
++TWDB=/var/lib/tripwire/YOUR_HOSTNAME.twd;
++TWSKEY=/etc/tripwire;
++TWLKEY=/etc/tripwire;
++TWREPORT=/var/lib/tripwire/report;
++#HOSTNAME=;
+ 
+ @@section FS
+ SEC_CRIT      = $(IgnoreNone)-SHa ;  # Critical files that cannot change
diff --git a/app-admin/tripwire/files/tripwire.txt b/app-admin/tripwire/files/tripwire.txt
index b29aa7ec21d9..4f47f8bd8196 100644
--- a/app-admin/tripwire/files/tripwire.txt
+++ b/app-admin/tripwire/files/tripwire.txt
@@ -1,82 +1,272 @@
-Introduction
-Tripwire v2.3 software ensures the integrity of critical system files and directories by identifying all changes made to specified system files and directories. Configure Tripwire software to monitor your system in the way that is best for you. 
+tripwire.txt					v. 11 Sept 2013
 
-Tripwire software works by comparing files and directories against a baseline. It generates the baseline by taking a "snapshot" of specified files and directories in a known secure state. Tripwire software then compares the current system against the baseline and reports any modifications, additions, or deletions. Use Tripwire software for system security, intrusion detection, damage assessment, and recovery forensics.
+Introduction to Tripwire, with Gentoo-specific installation information
 
-To install Tripwire v2.3
-1. Locate the RPM directory on the CD.
-2. Locate the Tripwire RPM.
-3. Type    rpm -i "name"
-4. After installing the Tripwire binary RPM, follow these Post-Installation instructions.
-5. We recommend you read the Release Notes and README file. 
+Tripwire software can monitor the integrity of critical system files and
+directories by identifying specified changes made to selected system
+files and directories. Configure Tripwire software to monitor your
+system in the way that is best for you.
 
-Post-Installation Instructions
-The Tripwire binary RPM installs the basic program files needed to run the software. However, this installation does not complete custom configurations that Tripwire 2.3 needs to perform correctly. After you unpack the RPM, you must:
-1. Run the configuration script: /etc/tripwire/twinstall.sh to sign these files. This script walks you through the processes of setting passphrases and signing the Tripwire policy and configuration files. 
-Note: Once encoded and signed, the configuration file should not be renamed or moved.
-2. Initialize the Tripwire database file. (/usr/sbin/tripwire--init)
-3. Run the first integrity check. (/usr/sbin/tripwire--check)
-4. Edit the configuration file (twcfg.txt) with a text editor, if desired.
-5. Edit the policy file (twpol.txt) with a text editor, if desired.
+Tripwire software works by comparing files and directories against a
+defined baseline, stored in a tripwire-created database. Tripwire
+generates the baseline by taking a "snapshot" of specified files and
+directories. Tripwire software then compares the current system against
+the baseline and reports modifications, additions, or deletions. Use
+Tripwire software for system security, intrusion detection, damage
+assessment, and recovery forensics.
 
-Note: If you plan to modify the policy file, we recommend you do so before running the configuration script. If you modify the policy file after running the configuration script, you must re-run the configuration file before initializing the database file. 
+
+To set-up Tripwire Configuration
+
+The Tripwire tarball installs the basic program files needed to run the
+software.  However, this installation does not prepare the configuration
+files that Tripwire needs to perform correctly. After you install the
+tripwire executable files and example configuration, you must:
+
+1. Review and perhaps edit the plain-text tripwire configuration file
+   (/etc/tripwire/twcfg.txt) with a text editor, if desired.
+
+2. Either run a configuration script (twsetup.sh from Gentoo's mktwpol
+   package, or tripwire-setup-keyfiles from Red Hat, or deprecated
+   twinstall.sh, also from Red Hat), or run the program `twadmin` with
+   the correct command line switches to make key files and encrypt/sign
+   the tripwire configuration file.
+
+   Make site key file
+   ------------------
+   `twadmin --generate-keys -S /etc/tripwire/site.key`
+
+   Make local key file
+   -------------------
+   `twadmin --generate-keys -L /etc/tripwire/$HOSTNAME-local.key`
+
+   Make mandatory signed tripwire configuration file (tw.cfg)
+   ----------------------------------------------------------
+   `twadmin --create-cfgfile -S /etc/tripwire/site.key /etc/tripwire/twcfg.txt`
+
+Note: Once encrypted/signed, the configuration file, tw.cfg, must not be
+renamed or moved.  The plain-text tripwire configuration file (twcfg.txt)
+should be deleted.  It can be recreated with `twadmin --print-cfgfile`
+
+3. Make a plain-text policy file.  The use of the name twpol.txt is
+   common, but the name of this file is not defined or used by Tripwire,
+   other than preparation of the encrypted/signed policy file.
+
+   To make the plain-text policy file, either run a policy file generator
+   (for example, mktwpol.sh from Gentoo's mktwpol package), or edit the
+   plain-text policy file (twpol-GENERIC.txt, or twpol.txt, or similar)
+   with a text editor.  The plain-text policy file should not refer to
+   any non-existent file or directory.
+
+   If you edit twpol-GENERIC.txt to act as your plain-text policy file,
+   provide your system's HOSTNAME at line 61.  If you don't provide
+   the correct HOSTNAME, a tripwire inspection of the target computer's
+   filesystem will fail to check the tripwire database file for changes.
+
+	TWDB=/var/lib/tripwire/YOUR_HOSTNAME.twd;
+
+4. Convert the plain-text policy file into the encrypted/signed form
+   that tripwire will refer to as it examines the files on the target
+   computer's filesystem.  The default filename for the encrypted/signed
+   policy file is defined in the tripwire configuration file (tw.cfg)
+   and is usually tw.pol.  The encryption/signing of plain-text twpol.txt
+   is done with yet another `twadmin` command line.
+
+   Make mandatory encrypted/signed system inspection policy file
+   --------------------------------------------------------------
+   `twadmin -m P -c /etc/tripwire/tw.cfg /etc/tripwire/twpol.txt`
+
+Note: If you modify the plain-text policy file after running the
+configuration script, you must re-sign the plain-text policy file before
+initializing the database file.  Tripwire baseline database creation and
+inspections refer to the encrypted/signed policy file, not to the
+plain-text policy file.
+
+Note: The plain-text tripwire policy file (twpol.txt) should be deleted.
+It can be recreated with `twadmin --print-polfile`
+
+5. Initialize the Tripwire database file.
+
+   Record current file attributes in the tripwire database
+   -------------------------------------------------------
+   `tripwire --init -c /etc/tripwire/tw.cfg`
+
+Note: Tripwire might issue some "Warning: File system error" errors,
+and appear to hang.  But as long as it follows with "### Continuing...",
+it is still working.
+
+6. Run the first integrity check.
+
+   `tripwire --check -c /etc/tripwire/tw.cfg`
+
+Note: The use of "-c /etc/tripwire/tw.cfg" is not required if Tripwire
+uses the default tripwire configuration directory and file names.  If
+you defer to tripwire default filenames, then updating a text policy
+file into a tripwire database, and running an integrity check, can be
+done with these commands:
+
+   `twadmin --create-polfile /etc/tripwire/twpol.txt`
+   `tripwire --init`
+   `tripwire --check`
 
 Modifying the Policy File
-You can specify how Tripwire software checks your system in the Tripwire policy file (twpol.txt). A default policy file is included in the Tripwire software installation. We recommend you tailor this policy file to fit your particular system. Tailoring the policy file greatly increases Tripwire software's ability to ensure the integrity of your system. 
 
-Locate the default policy file at  /etc/tripwire/twpol.txt. An example policy file (located at   /usr/doc/tripwire-VER#-REL#/policyguide.txt) is included to help you learn the policy language. Read the sample policy file and the comments in the sample policy file to learn the policy language. 
+How Tripwire software checks your system is specified in the Tripwire
+plain-text policy file (twpol.txt).  A default policy file is included in
+the Tripwire software installation.  This policy file should be tailored
+to fit your particular system.  Tailoring the policy file is necessary
+to take advantage of Tripwire software's ability to monitor changes on
+your system.
+
+The plain-text policy file is usually located at /etc/tripwire/twpol.txt.
+An example policy file (located at /etc/tripwire/twpol-GENERIC.txt, or
+at /usr/share/doc/tripwire-VER#-REL#/policyguide.txt) is included to
+help you learn the policy language.  Read the sample policy files and
+the comments in the sample policy file to learn the policy language.
+
+After you modify the plain-text policy file, don't forget!
+
+ encrypt/sign using `twadmin --create-polfile /etc/tripwire/twpol.txt`
 
-After you modify the policy file, follow the Post-Installation Instructions (run the configuration script). This script signs the modified policy file and renames it to tw.pol. This is the active policy file that runs as part of the Tripwire software. 
 
 Selecting Passphrases
-Tripwire files are signed or encrypted using site or local keys. These keys are protected by passphrases. When selecting passphrases, the following recommendations apply:
-Use at least eight alphanumeric and symbolic characters for each passphrase. The maximum length of a passphrase is 1023 characters. Quotes should not be used as passphrase characters.
 
-Assign a unique passphrase for the site key. The site key passphrase protects the site key, which is used to sign Tripwire software configuration and policy files. Assign a unique passphrase for the local key. The local key signs Tripwire database files. The local key may sign the Tripwire report files also. 
+Tripwire files are encrypted/signed using site or local keys. These keys
+are protected by passphrases. When selecting passphrases, the following
+recommendations apply:
+
+Use at least eight alphanumeric and symbolic characters for each
+passphrase. The maximum length of a passphrase is 1023 characters.
+Quotes should not be used as passphrase characters.
 
-Store the passphrases in a secure location. There is no way to remove encryption from a signed file if you forget your passphrase. If you forget the passphrases, the files are unusable. In that case you must reinitialize the baseline database.
+Assign a unique passphrase for the site key. The site key passphrase
+protects the site key, which is used to sign Tripwire software
+configuration and policy files. Assign a unique passphrase for the local
+key. The local key signs the Tripwire baseline database file. The local
+key may sign the Tripwire report files also.
+
+Store the passphrases in a secure location. There is no way to remove
+encryption from a signed file if you forget your passphrase and lost the
+key files.  If you forget the passphrases, the files are unusable. In
+that case you must create new key files and the baseline database.
+
+
+Initializing the Database
+
+In Database Initialization mode, Tripwire software builds a database of
+filesystem objects based on the rules in the policy file. This database
+serves as the baseline for integrity checks. The syntax for Database
+Initialization mode is:
+
+  `tripwire --init -c /etc/tripwire/tw.cfg`
 
-Initializing the Database 
-In Database Initialization mode, Tripwire software builds a database of filesystem objects based on the rules in the policy file. This database serves as the baseline for integrity checks. The syntax for Database Initialization mode is:
-tripwire  --init 
 
 Running an Integrity Check
-The Integrity Check mode compares the current file system objects with their properties recorded in the Tripwire database. Violations are printed to stdout. The report file is saved and can later be accessed by twprint. An email option enables you to send email. The syntax for Integrity Check mode is:
-tripwire --check 
+
+The Integrity Check mode compares the current file system objects with
+their properties recorded in the Tripwire database. Violations are
+printed to stdout. The report file is saved and can later be accessed by
+twprint. An email option enables you to send email. The syntax for
+Integrity Check mode is:
+
+  `tripwire --check -c /etc/tripwire/tw.cfg`
+
 
 Printing Reports - twprint Print Report Mode
-The twprint --print-report mode prints the contents of a Tripwire report. If you do not specify a report with the --twrfile or -r command-line argument, the default report file specified by the configuration file REPORTFILE variable is used. 
-Example: On a machine named LIGHTHOUSE, the command would be:
-./twprint -m r --twrfile LIGHTHOUSE-19990622-021212.twr
+
+The twprint --print-report mode prints the contents of a Tripwire
+report. If you do not specify a report with the --twrfile or -r
+command-line argument, the default report file specified by the
+configuration file REPORTFILE variable is used.
+
+Example: On a machine named LIGHTHOUSE, the command could be:
+
+  `twprint -m r --twrfile LIGHTHOUSE-19990622-021212.twr`
+
 
 Updating the Database after an Integrity Check
-Database Update mode enables you to update the Tripwire database after an integrity check if you determine that the violations discovered are valid. This update process saves time by enabling you to update the database without having to re-initialize it. It also enables selective updating, which cannot be done through re-initialization. The syntax for Database Update mode is:
-tripwire --update 
+
+Database Update mode enables you to update the Tripwire database after
+an integrity check if you determine that the violations discovered are
+valid. This update process saves time by enabling you to update the
+database without having to re-initialize it. It also enables selective
+updating, which cannot be done through re-initialization. The syntax for
+Database Update mode is:
+
+  `tripwire --update`
+
 
 Updating the Policy File
-Change the way that Tripwire software scans the system by changing the rules in the policy file. You can  then update the database without a complete re-initialization. This saves a significant amount of time and preserves security by keeping the policy file synchronized with the database it uses.  The syntax for Policy Update mode is:
-tripwire  --update-policy 
+
+Change the way that Tripwire software scans the system by changing the
+rules in the policy file.  You can then update the database without a
+complete re-initialization. This saves a significant amount of time and
+preserves security by keeping the policy file synchronized with the
+database it uses.  The syntax for Policy Update mode is:
+
+  `tripwire  --update-policy`
+
 
 Testing email functions
-Test mode tests the software's email notification system, using the settings currently specified in the configuration file. The syntax for Email Test Reporting mode is:
-tripwire  --test 
+
+Test mode tests the software's email notification system, using the
+settings currently specified in the configuration file. The syntax for
+Email Test Reporting mode is:
+
+  `tripwire  --test`
+
 
 Tripwire Components
-The policy file begins as a text file containing comments, rules, directives, and variables. These dictate the way Tripwire software checks your system. Each rule in the policy file specifies a system object to be monitored. Rules also describe which changes to the object to report, and which to ignore. 
 
-System objects are the files and directories you wish to monitor. Each object is identified by an object name. A property refers to a single characteristic of an object that Tripwire software can monitor. Directives control conditional processing of sets of rules in a policy file. During installation, the text policy file is encrypted and renamed, and becomes the active policy file. 
+The policy file begins as a text file containing comments, rules,
+directives, and variables. These dictate the way Tripwire software
+checks your system. Each rule in the policy file specifies a system
+object to be monitored. Rules also describe which changes to the object
+to report, and which to ignore.
 
-The database file is an important component of Tripwire software. When first installed, Tripwire software uses the policy file rules to create the database file. The database file is a baseline "snapshot" of the system in a known secure state. Tripwire software compares this baseline against the current system to determine what changes have occurred. This is an integrity check.
+System objects are the files and directories you wish to monitor. Each
+object is identified by an object name. A property refers to a single
+characteristic of an object that Tripwire software can monitor.
+Directives control conditional processing of sets of rules in a policy
+file. During installation, the text policy file is encrypted/signed and
+renamed, and becomes the active policy file.
 
-When you perform an integrity check, Tripwire software produces report files. Report files summarize any changes that violated the policy file rules during the integrity check. You can view the report file in a variety of formats, at varying levels of detail.  
+The database file is an important component of Tripwire software. When
+first installed, Tripwire software uses the policy file rules to create
+the database file. The database file is a baseline "snapshot" of the
+system in a known secure state. Tripwire software compares this baseline
+against the current system to determine what changes have occurred. This
+is an integrity check.
+
+When you perform an integrity check, Tripwire software produces report
+files. Report files summarize any changes that violated the policy file
+rules during the integrity check. You can view the report file in a
+variety of formats, at varying levels of detail.
+
+The Tripwire configuration file stores system-specific information, such
+as the location of Tripwire data files. Tripwire software generates some
+of the configuration file information during installation. The system
+administrator can change parameters in the configuration file at any
+time. The configuration file variables POLFILE, DBFILE, REPORTFILE,
+SITEKEYFILE, and LOCALKEYFILE specify where the policy file, database
+file, report files, and site and local key files reside. These variables
+must be defined or the configuration file is invalid. If any of these
+variables are undefined, an error occurs on execution of Tripwire
+software and the program exits.
 
-The Tripwire configuration file stores system-specific information, such as the location of Tripwire data files. Tripwire software generates some of the configuration file information during installation. The system administrator can change parameters in the configuration file at any time. The configuration file variables POLFILE, DBFILE, REPORTFILE, SITEKEYFILE, and LOCALKEYFILE specify where the policy file, database file, report files, and site and local key files reside. These variables must be defined or the configuration file is invalid. If any of these variables are undefined, an error occurs on execution of Tripwire software and the program exits. 
 
 Tripwire Help
-All Tripwire commands support the help arguments. Example: To get help with Create Configuration File mode, type: ./twadmin --help --create-cfgfile
 
--?		Display usage and version information
---help		Display all command modes
---help all	Display help for all command modes
---help [mode]	Display help for current command mode
---version	Display version information
+All Tripwire commands support the help arguments.
+
+Example: To get help with Create Configuration File mode, type:
+
+  `twadmin --help --create-cfgfile`
+
+  -?			Display usage and version information
+  --help		Display all command modes
+  --help all		Display help for all command modes
+  --help [mode]		Display help for current command mode
+  --version		Display version information
+
+We recommend you read the Tripwire Release Notes and README file.
diff --git a/app-admin/tripwire/metadata.xml b/app-admin/tripwire/metadata.xml
index 1dad6e025bfc..be62dd957018 100644
--- a/app-admin/tripwire/metadata.xml
+++ b/app-admin/tripwire/metadata.xml
@@ -22,6 +22,8 @@
 		que se pueden adoptar medidas de control de forma periódica.
 	</longdescription>
 	<use>
+		<flag name="setup">Installs mktwpol package including scripts for
+		tripwire installation/setup and tripwire database maintenance</flag>
 		<flag name="ssl">Adds support for Secure Socket Layer connections</flag>
 		<flag name="static">Builds the package statically</flag>
 	</use>
diff --git a/app-admin/tripwire/tripwire-2.4.2.2-r2.ebuild b/app-admin/tripwire/tripwire-2.4.2.2-r2.ebuild
new file mode 100644
index 000000000000..3e6c7eca469a
--- /dev/null
+++ b/app-admin/tripwire/tripwire-2.4.2.2-r2.ebuild
@@ -0,0 +1,79 @@
+# Copyright 1999-2013 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Header: /var/cvsroot/gentoo-x86/app-admin/tripwire/tripwire-2.4.2.2-r2.ebuild,v 1.1 2013/09/25 08:45:54 nimiux Exp $
+
+EAPI=5
+
+inherit autotools eutils flag-o-matic
+
+DESCRIPTION="Open Source File Integrity Checker and IDS"
+HOMEPAGE="http://www.tripwire.org/"
+SRC_URI="mirror://sourceforge/tripwire/tripwire-${PV}-src.tar.bz2"
+
+LICENSE="GPL-2"
+SLOT="0"
+KEYWORDS="~amd64 ~ppc ~x86 ~x86-fbsd"
+IUSE="ssl static setup"
+
+DEPEND="sys-devel/automake
+	sys-devel/autoconf
+	ssl? ( dev-libs/openssl )"
+RDEPEND="virtual/cron
+	virtual/mta
+	ssl? ( dev-libs/openssl )"
+PDEPEND="setup? ( app-admin/mktwpol )"
+
+S="${WORKDIR}"/tripwire-"${PV}"-src
+
+src_prepare() {
+	epatch "${FILESDIR}"/"${P}"-fix-configure.patch
+	epatch "${FILESDIR}"/"${P}"-buildnum.patch
+	epatch "${FILESDIR}"/"${P}"-gcc-4.7.patch
+	epatch "${FILESDIR}"/"${P}"-twpol-GENERIC.patch
+
+	eautoreconf
+}
+
+src_configure() {
+	# tripwire can be sensitive to compiler optimisation.
+	# see #32613, #45823, and others.
+	# 	-taviso@gentoo.org
+	strip-flags
+	append-cppflags -DCONFIG_DIR='"\"/etc/tripwire\""' -fno-strict-aliasing
+	econf $(use_enable ssl openssl) $(use_enable static)
+}
+
+src_install() {
+	dosbin "${S}"/bin/{siggen,tripwire,twadmin,twprint}
+	doman "${S}"/man/man{4/*.4,5/*.5,8/*.8}
+	dodir /etc/tripwire /var/lib/tripwire{,/report}
+	keepdir /var/lib/tripwire{,/report}
+
+	exeinto /etc/cron.daily
+	doexe "${FILESDIR}"/tripwire
+
+	dodoc ChangeLog policy/policyguide.txt TRADEMARK \
+		"${FILESDIR}"/tripwire.txt
+
+	insinto /etc/tripwire
+	doins "${FILESDIR}"/twcfg.txt policy/twpol-GENERIC.txt
+
+	fperms 750 /etc/cron.daily/tripwire
+}
+
+pkg_postinst() {
+	if [[ -z ${REPLACING_VERSIONS} ]] ; then
+		elog "Tripwire needs to be configured before its first run. You can"
+		elog "do this by manually editing the twpol-GENERIC.txt file shipped with"
+		elog "the package to suit your needs. A quickstart guide is provided"
+		elog "in tripwire.txt file to help you with this."
+		elog "To configure tripwire automatically, you can use the twsetup.sh"
+		elog "script provided by the app-admin/mktwpol package. This package is"
+		elog "installed for you if you append \"setup\" to your USE flags."
+else
+		elog "Maintenance of tripwire policy files as packages are added"
+		elog "and deleted from your system can be automated by the mktwpol.sh"
+		elog "script provided by the app-admin/mktwpol package. This package"
+		elog "is installed for you if you append \"setup\" to your USE flags"
+	fi
+}