Bug 156614

Summary:	split nut package
Product:	[openSUSE] openSUSE 10.2	Reporter:	Stanislav Brabec <sbrabec>
Component:	Basesystem	Assignee:	Stanislav Brabec <sbrabec>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	suse+build
Version:	unspecified
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Stanislav Brabec 2006-03-09 17:46:00 UTC

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

Comment 1 Stanislav Brabec 2006-03-20 17:02:26 UTC

Many changes were done in current nut packaging. Remaining issues are:
- SuSE packages everything in one big RPM
- udev integration

Comment 2 Stanislav Brabec 2006-04-26 10:28:20 UTC

udev integration is impossible and we need different solution - see bug 168611, now fixed.

The remaining issue is splitting the package.

Comment 3 Stanislav Brabec 2008-05-09 10:22:01 UTC

udev integration already works. Splitted out nut-cgi and nut-drivers-net for openSUSE 11.0. Splitting to more subpackages does not make sense for non-embedded systems.