[Bug 562470] Review Request: openvas-client - Client component of Open Vulnerability Assessment (OpenVAS) Scanner

[bugzilla at redhat.com]

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 #11 from Xavier Bachelot <xavier at bachelot.org> 2010-04-16 18:43:44 EDT ---
(In reply to comment #10)

> 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.
> 
Agreed, a lower-case symlink would be handy.

> 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&group_id=29&atid=220
> 
This fixes it and could be included as a patch :
http://wald.intevation.org/plugins/scmsvn/viewcvs.php/trunk/openvas-client/openvas/latex_output.c?root=openvas&rev=7137&r1=5830&r2=7137&makepatch=1&diff_format=h

> 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.
> 
If it doesn't drag too much dependencies, it probably should. What happens if
you try to use this feature and htmldoc is not available ?

-- 
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.