I intended to create a fvwm-themes RPM. I looked into webalizer and fvwm2 specs and I didnt beleive my eyes: the program is first unpacked and built and then some of the resulting binaries are one by one installed _manually_ from the spec. Thats probably the reason why webasolve doesnt work (it should be named webazolver) and fvwm-themes doesnt compile (it needs fvwm-config which is not manually installed). Or do I need nonexistent fvwm2-devel package for compilation of fvwm-themes? To automate the install process I'd suggest patched install which installs into $RPM_BUILD_ROOT/dir instead of /dir (which should not affect normal installs unless RPM_BUILD_ROOT is manually set)
-- Michal Suchanek [EMAIL PROTECTED]