> Yes, because for now I am submitting the patch I am generating from the build I submit to my PPA to test.
FWIW, the convention for ppa uploads is to append ~ppaX to the new version number. > Yes, this is done intentionally because AFAIU the static lib is not supposed to be used by consumers of libtraceevent Ah, okay. This was causing me a lot of confusion, since you are kind of mis-using the LIBTRACEEVENT_STATIC variable. The point remains either way that you should simply use -ltraceevent (this is what any real consumer will do) instead of grepping `dpkg -L`. If you want to keep using LIBTRACEEVENT_STATIC for this purpose, please add a comment explaining that we are knowingly hijacking this variable to instead link against the shared library. Otherwise, it will continue to be confusing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051916 Title: [MIR] promote libtraceevent as a trace-cmd dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtraceevent/+bug/2051916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
