I have the -X useflag set system wide, but OpenVAS wants to install all kinds of X stuff Reproducible: Always Steps to Reproduce: ~ # emerge -pt openvas These are the packages that would be merged, in reverse order: Calculating dependencies... done! [ebuild N ] net-analyzer/openvas-1.0.1 [ebuild N ] net-analyzer/openvas-client-1.0.4 [ebuild N ] x11-libs/gtk+-2.12.11 USE="jpeg tiff vim-syntax -X -cups -debug -doc -xinerama" [ebuild N ] app-vim/gtk-syntax-20060423 [ebuild N ] x11-libs/libXcomposite-0.4.0 USE="-debug" [ebuild N ] x11-proto/compositeproto-0.4 [ebuild N ] x11-libs/libXrandr-1.2.2 USE="-debug" [ebuild N ] x11-proto/randrproto-1.2.1 [ebuild N ] x11-libs/pango-1.20.5 USE="-X -debug -doc" [ebuild N ] dev-util/gtk-doc-am-1.10-r1 [ebuild N ] x11-misc/shared-mime-info-0.30 [ebuild N ] x11-libs/libXdamage-1.1.1 USE="-debug" [ebuild N ] dev-libs/atk-1.22.0 USE="-debug -doc" [ebuild N ] x11-libs/libXi-1.1.3 USE="-debug" [ebuild N ] x11-libs/libXcursor-1.1.9 USE="-debug" [ebuild N ] x11-libs/libXfixes-4.0.3 USE="-debug" [ebuild N ] x11-proto/fixesproto-4.0 [ebuild N ] x11-libs/cairo-1.6.4-r1 USE="-X -debug -directfb -doc -glitz -opengl -svg -test -xcb" [ebuild N ] x11-libs/pixman-0.10.0 USE="-debug" [ebuild N ] net-analyzer/openvas-plugins-1.0.4 [ebuild N ] net-analyzer/openvas-server-1.0.2 USE="tcpd -debug -gtk -prelude" [ebuild N ] net-analyzer/openvas-libnasl-1.0.1 [ebuild N ] net-analyzer/openvas-libraries-1.0.2 [ebuild N ] net-libs/gnutls-2.4.1-r2 USE="zlib -bindist -doc -guile -lzo -nls" [ebuild N ] dev-libs/libtasn1-1.3 USE="-doc" [ebuild N ] app-crypt/gpgme-1.1.6 USE="-pth" [nomerge ] x11-libs/libXdamage-1.1.1 USE="-debug" [ebuild N ] x11-proto/damageproto-1.1.0 [nomerge ] x11-libs/libXi-1.1.3 USE="-debug" [ebuild N ] x11-libs/libXext-1.0.3 USE="-debug" ~ # Actual Results: x-11 stuff is emerged Expected Results: x-11 stuff should not be emerged
I think the point of emerging net-analyzer/openvas is to install all the net-analyzer/openvas-* packages, including net-analyzer/openvas-client which would obviously pull in all those X dependencies. If you only need the server component, then you could simply emerge net-analyzer/openvas-server instead. But then this sort of confusion could be avoided by improving the package Descriptions. The first one is a meta-package - its description could clarify that: [N] net-analyzer/openvas (~1.0.1): A remote security scanner [N] net-analyzer/openvas-client (~1.0.4): A client for the openvas vulnerability scanner [N] net-analyzer/openvas-libnasl (~1.0.1): A remote security scanner for Linux (openvas-libnasl) [N] net-analyzer/openvas-libraries (~1.0.2): A remote security scanner for Linux (openvas-libraries) [N] net-analyzer/openvas-plugins (~1.0.4): A remote security scanner for Linux (openvas-plugins) [N] net-analyzer/openvas-server (~1.0.2): A remote security scanner for Linux (openvas-server)
I understand that, but need the client for command line intergration into my AutoNessus. Accoording to this post you can compilte the client without gtk support: http://lists.wald.intevation.org/pipermail/openvas-discuss/2008-November/000792.html by passing the "--disable-gtk" parameter to configure. Like the nessus-client package, this package should also accept the -X -gtk USE flags.
Added gtk use flag, if you want openvas without X, emerge with USE="-gtk"
