I tried to run dwww on a redhat system and I got a couple of errors:
a) dwww assumes dpkg. The source packages doesn't look like a Debian-only
   source, so either dwww should become debian-only or support for rpm
   should be added (not very hard)
b) dwww assumes man-db is installed and depends on `manpath' in dwww-build.
   If someone uses another man-system dwww-build should fall back on a
   hardcoded path.

Wichert.

<wichert@wi.leidenuniv.nl> writes:

Yes, I am planning that for the next (experimental) release.  I've got a
Red Hat system here now too, so at least I can test it.  It will be a good
opportunity to learn RPM for me.  (Hopefully I'll get some ideas on how
to improve dpkg)

I'll probably re-do the source using autoconf/automake - so it should be
fairly portable.

Actually, part of my grand scheme is to use the (still vapourware)
experimental dwww engine I'm going to build in behind the scenes on the
LinuxHQ website.  I hope to be able to build a network where I can have the
documentation (and source code) for every Debian, RedHat and SunSite
package on-line on the web - plus a bunch of other stuff too.

Yes, of course.  I'll make sure I do that.

Thanks for the report.

Cheers,

 - Jim

<wichert@wi.leidenuniv.nl> writes:

Yes, I am planning that for the next (experimental) release.  I've got a
Red Hat system here now too, so at least I can test it.  It will be a good
opportunity to learn RPM for me.  (Hopefully I'll get some ideas on how
to improve dpkg)

I'll probably re-do the source using autoconf/automake - so it should be
fairly portable.

Actually, part of my grand scheme is to use the (still vapourware)
experimental dwww engine I'm going to build in behind the scenes on the
LinuxHQ website.  I hope to be able to build a network where I can have the
documentation (and source code) for every Debian, RedHat and SunSite
package on-line on the web - plus a bunch of other stuff too.

Yes, of course.  I'll make sure I do that.

Thanks for the report.

Cheers,

 - Jim