Group :: File tools
RPM: pdbv
Main Changelog Spec Patches Sources Download Gear Bugs and FR Repocop
Current version: 2.0.9-alt1
Build date: 4 february 2009, 08:22 ( 796.7 weeks ago )
Size: 109.91 Kb
Home page: http://gna.org/projects/pdbv
License: GPLv2+
Summary: Pdbv output a HTML view of a RPM or dpkg database
Description:
List of contributors List of rpms provided by this srpm:
ACL:
Build date: 4 february 2009, 08:22 ( 796.7 weeks ago )
Size: 109.91 Kb
Home page: http://gna.org/projects/pdbv
License: GPLv2+
Summary: Pdbv output a HTML view of a RPM or dpkg database
Description:
Pdbv output a HTML view of a RPM or dpkg database. Its modular design
allows easy addition of others package management database and export
format (as xml).
Why using it:
- it does not require lucid/gtk+/qt or other big libs.
- it does not require a web server - but it can be used with a web
server, as any
other html files.
- it does not require a X server running, you can use a text mode
browser that support
frames as links.
- it does not require special privileges to access to the output. But
access can
be restricted by using chmod/chown (filesystem) or .htaccess
(apache).
- since output is generated by a cronjob, access to the output is as
fast as your
computer is able to read/serve text files.
Why not using it:
- it's purpose is not to manage packages installed.
- since output is generated by a cronjob, informations are dated, and
can be
outdated if the database change very frequently. Note that with the
2.x.x series,
the cronjob should be hourly.
You can see demos at http://dl.gna.org/pdbv/demo_html/
Current maintainer: Eugeny A. Rostovtsev (REAL) allows easy addition of others package management database and export
format (as xml).
Why using it:
- it does not require lucid/gtk+/qt or other big libs.
- it does not require a web server - but it can be used with a web
server, as any
other html files.
- it does not require a X server running, you can use a text mode
browser that support
frames as links.
- it does not require special privileges to access to the output. But
access can
be restricted by using chmod/chown (filesystem) or .htaccess
(apache).
- since output is generated by a cronjob, access to the output is as
fast as your
computer is able to read/serve text files.
Why not using it:
- it's purpose is not to manage packages installed.
- since output is generated by a cronjob, informations are dated, and
can be
outdated if the database change very frequently. Note that with the
2.x.x series,
the cronjob should be hourly.
You can see demos at http://dl.gna.org/pdbv/demo_html/
List of contributors List of rpms provided by this srpm:
- pdbv