From Fedora Project Wiki
Line 24: Line 24:
== How To Test ==
== How To Test ==
No special hardware is needed.
No special hardware is needed.
Automated test suite is not available yet (even if it is needed), but all the commands should behave according to the man page. Usually just basic operations need to be tested, since it's almost impossible to test all features manually due to the complexity of the tools.
Automated test suite is not available yet (even if it is needed), but all the commands should behave according to the man page. Usually just basic operations need to be tested, since it's very ineffective to test all the features manually due to the complexity of the tools.


== User Experience ==
== User Experience ==

Revision as of 16:33, 9 May 2012

procps-ng

Summary

Migration from legacy procps tools to procps-ng (next generation procps tools).

Owner

Current status

  • Targeted release: Fedora 18
  • Last updated: 2012-03-07
  • Percentage of completion: 100%

Detailed Description

Old (legacy) procps tools had no updates for several years and that led to a massive code split caused by a local-only application of distribution specific patches, which were not merged upstream. The project became hardly maintainable since some of the newly written patches were incompatible with sources maintained by other distributors. A similar incompatibility could be noticed in the applications behaviour and their command line switches. This inevitable update can be understood as an effort to unify the procps tools across all Linux distributions.

Benefit to Fedora

Better maintainability.

Scope

Even if there are more then 30 packages depending on the procps tools, the change shouldn't have major negative impact on the dependent packages. The package just needs to be built and it's basic functions tested.

How To Test

No special hardware is needed. Automated test suite is not available yet (even if it is needed), but all the commands should behave according to the man page. Usually just basic operations need to be tested, since it's very ineffective to test all the features manually due to the complexity of the tools.

User Experience

Dependencies

Contingency Plan

Documentation

Release Notes

Comments and Discussion