RPM

The ISPRAS 'upstream tracker'

Registered by herrold

The new service for tracking ABI changes in various C/C++ libraries is now available for Linux distribution maintainers and upstream developers - "Upstream Tracker". It may be helpful for analyzing risks of libraries updating in the CentOS and other systems.

Blueprint information

Status:
Complete
Approver:
Denis Silakov
Priority:
Medium
Drafter:
Denis Silakov
Direction:
Approved
Assignee:
Denis Silakov
Definition:
Discussion
Series goal:
Accepted for 5.3
Implementation:
Implemented
Milestone target:
None
Started by
Jeff Johnson
Completed by
Jeff Johnson

Related branches

Sprints

Whiteboard

The upstream abi checker (as included in RPM) needs several additional files.

On linux, there's likely no need to distribute/maintain within rpm (per-Ponomarenko)
a separate package is easier to update (but there are distress w/o separate packaging).

OTOH, rpmbuild is ideally positioned to be able to generate the ABI markup incrementally.
That would necessitate a tighter coupling between rpm build <-> abi checker rather than
a standalone tool.

However, it is believed that all rpmbuild should do is to invoke abi-compliance-checker.pl with proper input. It is doubtful that rpmbuild should be tightly coupled to internal structure of the script, even to implement some smart cooperation. So it should not matter how abi-compliance-checker is installed - by a separate package or together with rpm-build. And in this case it is much more easier to update abi-checker (given that it doesn't change format of input data).

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

Nearby

This blueprint contains Public information 
Everyone can see this information.