On Mon, Sep 03, 2012 at 01:02:33PM +0200, Petr Gajdůšek wrote: > I'm looking forward to the new API! Is there already any > discussion/code? There is some discussion on the procps list at http://www.freelists.org/archive/procps/
There is some wiki words around the API at https://gitorious.org/procps/pages/The_libprocps_redesign > Until it happens, it depends on how big is the issue with ulatencyd > embedding own libproc copy. If you decide to export those symbols, I > could prepare patches fixing #682712 instantly. The patches would make the API change dramatically in a way completely opposite to where the API is heading. For example the vminfo() function and variables are rarely used and of those we use 4. If I was you, I'd first check if those symbols are really used (they're just exported to LUA variables) and write some code that grabbed the ones I needed. After all, its a matter of just reading /proc/vmstat > As I am thinking of this, I incline to embed verbatim copy of current > libproc, write minimal header file to be used by ulatencyd code to > ensure minimum symbols will be used and make configurable the use of > external libprocps (patched to export enough symbols). procps library code is LGPL v2.1 so you can link it to GPL v3 which your program uses, so yes you could lift and modify it. - Craig -- Craig Small VK2XLZ http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
