|
Bugzilla – Full Text Bug Listing |
| Summary: | NUT - classic and HAL versions should not be packaged together | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Arjen de Korte <suse+build> |
| Component: | Other | Assignee: | Stanislav Brabec <sbrabec> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Arjen de Korte
2007-10-26 12:33:52 UTC
Could you counfirm, that I understand correctly the purpose? 1) None of them should be preferred: nut-hal will be used for local USB UPSes. In all other cases nut-classic will be needed: Serial UPSes, SNMP remote UPSes, combination of UPSes. The disadvantage of nut-classic is impossibility of reuse of HAL power management frontends. 2) It seems to be a temporary solution. We can get rid hal-classic, if: - All drivers will be moved to HAL. For undetectable hardware it will require config based static HAL provider, which does not exist yet (It was rejected in past by some developers as "against the spirit of hal". Now they have more positive opinion about it, but somebody must write it.) - The network UPS logic will be integrated with HAL. It may need a consesus with an extension of hal power management. Package was already splitted as expected. I forgot to add Requires: for the frontend into the core packages. Fixing now. It introduces circular dependency between core and frontend package, but it is intended. One without the other cannot be used. |