[Bug 211043] Review Request: vdradmin-am - Web interface for VDR

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

Summary: Review Request: vdradmin-am - Web interface for VDR


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=211043





------- Additional Comments From ville.skytta at iki.fi  2006-10-20 03:05 EST -------
(In reply to comment #1)

> If the log files were enabled would they provide any usefull information?

I guess that depends on what one considers useful.  Logging is disabled by 
default upstream too, and I don't remember ever enabling it myself during the 
few years I've used vdradmin.

> W: vdradmin-am dangerous-command-in-%postun rm
> 
> I wish there was a way to avoid this. Is the cache directory multi-level?
> or single directory of files? If so, you can remove the -r from the rm at
> least.

That depends on how perl-Template-Toolkit works.  Currently it creates the 
same dir structure as where the templates are to below /var/cache/vdradmin, 
ie. /var/cache/vdradmin/usr/share/vdradmin/template/...  Leaving 
the "compiled" templates there should not break anything, but will leave trash 
behind as upstream templates are renamed/removed on upgrades, as well as on 
final removal.

> 2. Should this package require 'httpd' or 'webserver' ?

No.  vdradmin-am is a standalone app-specific webserver itself.  There's just 
an example config snippet in docs which can be used to proxy it behind Apache.

> 3. Should the description mention that you need a vdr install somewhere in 
> order for this package to be usefull?

Well, it already says "VDRAdmin-AM is a web interface for managing VDR" so I 
suppose it's pretty clear that in order for it to be useful, VDR is needed 
somewhere.  Improvement suggestions to %description are welcome, though.

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.