Hello,

I have seriously lost track (or maybe never knew) about why we use filteremerge?
The output doesn't seem that special (overly verbose) and it is just another
layer of uneeded abstraction, in my opinion. So, what output do we really
need/want to see? It has been suggested that all einfo/elog/ewarn output is
displayed and the build.log if there is a failure. Great! Portage can handle
this itself with the --quiet-build=y option.


% sudo EMERGE_DEFAULT_OPTS="" emerge --quiet-build=y -1 vim 
Calculating dependencies... done!
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) app-editors/vim-7.3.266
>>> Installing (1 of 1) app-editors/vim-7.3.266
>>> Jobs: 1 of 1 complete                           Load avg: 1.39, 0.50, 0.29

 * Messages for package app-editors/vim-7.3.266:

 * To install a GUI version of vim, use the app-editors/gvim
 * package.
 * Vim 7 includes an integrated spell checker. You need to install
 * word list files before you can use it. There are ebuilds for
 * some of these named app-vim/vim-spell-*. If your language of
 * choice is not included, please consult vim-spell.eclass for
 * instructions on how to make a package.
(this is ewarn) * Note that the English word lists are no longer installed by
(this is ewarn) * default.
 * To see what's new in this release, use :help version7.txt
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.

 * GNU info directory index is up-to-date.


--- a/cfengine/inputs/cfagent.conf
+++ b/cfengine/inputs/cfagent.conf
@@ -27,8 +27,8 @@ control:
 
         # Portage settings
         DefaultPkgMgr         = ( portage )
-        PortageInstallCommand = ( "/usr/local/bin/filteremerge %s" )
-        PortageRemoveCommand  = ( "/usr/local/bin/filteremerge -C %s" )
+        PortageInstallCommand = ( "/usr/bin/emerge  --quiet-build=y --color=n %s" )
+        PortageRemoveCommand  = ( "/usr/bin/emerge --quiet-build=y -qC %s" )
 
         # custom variables
         masterfiles = ( /var/cfengine-new/repository/files )

-Jeremy