Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=562470
--- Comment #10 from Michal Ambroz <rebus(a)seznam.cz> 2010-03-25 15:35:07 EDT ---
Hello,
I was testing the openvas-client so here are my 2 copper coins:
1) inconsistency in naming between the openvas packages
Most tools in openvas suite are named openvas-something except the client
OpenVAS-Client .
The discrepancy is comming from the upstream package.
I would recommend to create symbolic link openvas-client just for comfort - big
letters are sexy, but could be hard to remember when all the other tools from
the suite are lowercase.
2) OpenVAS-Client is crushing with export to LaTeX of empty report
reported upstream
http://wald.intevation.org/tracker/index.php?func=detail&aid=1343&...
3) Export to pdf requires htmldoc
As report to pdf won't be probably the main exports used,
however there is question whether there should be rpm dependency
added to the spec file.
Best regards
Michal Ambroz
--
Configure bugmail:
https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.