[procps] Re: procps-ng version 3.3.4 released
- From: Jim Warner <james.warner@xxxxxxxxxxx>
- To: procps@xxxxxxxxxxxxx
- Date: Tue, 30 Oct 2012 08:33:24 -0500
On Oct 30, 2012, at 5:31 AM, Craig Small <csmall-procps@xxxxxxxxxx> wrote:
> The API changed which has caused all sorts of dramas. I didn't think we
> had made the change but its there. I'll be making a 3.3.5 release
> tonight that basically bumps the API SONAMES.
Hi Craig,
Below is an excerpt from an earlier email I sent to you (but not freelists)
detailing the API/ABI issues.
Additionally, the following commit message also referenced a broken ABI:
commit 6c8e9d95818bb4f5dbe18ee509e5d5c326bc06c5
Regards,
Jim
--------------------------------------------------
On Aug 21, 2012, at 4:36 PM, Jim Warner <james.warner@xxxxxxxxxxx> wrote:
> ...
> The 3 embedded tarballs are designed to be applied in sequence, if at all.
> They also represent increasing levels of library impact.
>
> 1.scroll+misc.tgz
> This one has no impact on the library API or ABI. Any library changes are
> strictly internal but the libtool guidelines suggest a new 'revision' number
> is needed anyway. In any case, these commits contain some useful top
> enhancements and performance improvements. There is also one for a yet to be
> reported ps bug (it's actually #0001, the very first commit).
>
> 2.environment.tgz
> This one assumes the first tarball has been applied. It provides much more
> flexible access to a task's environment than that available via ps. It does,
> however, alter the library API by adding new flag. It is backward compatible
> for existing code but may deserve a new library 'age' designation, as a
> minimum.
>
> 3.pg-fault-deltas.tgz
> This one assumes the second tarball has been applied. It addresses Debian
> bug/wishlist #84992. But, while the library API is unchanged, it breaks the
> ABI with additional proc_t fields. I guess it would require a new 'current'
> designation.
> ...
Other related posts:
