I forgot to CC the bug tracker, sorry... Craig Small píše v St 29. 08. 2012 v 18:28 +1000: > What is the sort of time you are looking at for all of this? I'd prefer > not to expose more symbols that we are then going to remove reasonably > soon, but if you need them in the interim then I can arrange something. > > Please note they will definitely be going, but we can certainly work > together to make sure your program uses the new API. > > - Craig
Hello Craig, I'm looking forward to the new API! Is there already any discussion/code? 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. On the other side, ulatencyd upstream must use embedded copy of libprocps until the planned new API - or current API with enough exported symbols - will be widely available 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). - Petr -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
