Comments from Arnaud Quette and Arjen de Korte:

- the generated startup scripts include upslog, but still with the old commands for startup. Which means that enabling
upslog in /etc/sysconfig/smartups means that the startup script will 
throw an error. Since there is no quick fix for that, I removed the
scripting support for upslog from this. This point will be addressed by NPS.

- SuSE packages everything in one big RPM. It would be better, while waiting for the NPS, to separate the CGI part, and maybe the snmp part. 
I don't see much interest in separating upsd/drivers and upsmon as the later is not really big in size...

- SuSE uses --ups-user=nobody which is ugly. I would advice for a nut or ups user. This point is discussed in the NPS 

- the permissions should be a little tighter on some files and dir.

- the configuration generated by SuSEconfig.nut (which
is supposed to generate the required configuration files from
/etc/sysconfig/smartups) doesn't work, since the contents of the 
generated ups.conf and upsmon,conf don't use consistent naming. At the
very least, it should be able to setup a working configuration to
monitor a UPS connected to the local machine without having to worry
about setting up passwords and users and so on. Currently, it doesn't. 

- I'm also facing some udev integration problems on SuSE 10. Help welcomed...

- seamless upgrade: The problem lies in the changing of ownership/permissions on
existing configuration files and the /var/run/ups and /var/lib/ups
directories. Not changing the ownership/permissions on the configuration
files is one way to deal with part of this problem. For the directories,
there are probably nifty RPM macro's to deal with that