Features/procps-ng

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(How To Test)
(How To Test)
Line 23: Line 23:
  
 
== How To Test ==
 
== How To Test ==
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
 
 
Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
 
 
A good "how to test" should answer these four questions:
 
 
0. What special hardware / data / etc. is needed (if any)?
 
1. How do I prepare my system to test this feature? What packages
 
need to be installed, config files edited, etc.?
 
2. What specific actions do I perform to check that the feature is
 
working like it's supposed to?
 
3. What are the expected results of those actions?
 
-->
 
 
 
No special hardware is needed.
 
No special hardware is needed.
 
Automated test suite is not available yet, but all the commands should behave according to the man page.
 
Automated test suite is not available yet, but all the commands should behave according to the man page.

Revision as of 16:29, 9 May 2012

Contents

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, but all the commands should behave according to the man page.

User Experience

Dependencies

Contingency Plan

Documentation

Release Notes

Comments and Discussion