-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maybe UNIX-way name for .so library ? #16
Comments
This would need further changes in the documentation and the wrapper script. @onlyjob, what do you think about the general idea? Personally, I think the “lib” prefix is misleading, since the shared object only overrides functions and cannot really be “used” like another library… |
Then better nocache-wrapper, than libnocache.so, |
I'm with you @Feh as I also don't recognise the value of this change. I actually prefer name "nocache.so" since it is a good match for executable while it is not a library so we can't comply with policy regarding SONAME (and/or ABI/API) anyway. In Debian we install "nocache.so" to private location under |
+1 for storing nocache.so (or nocache-wrapper) in /usr/lib/nocache/ . |
:) On Debian it is also a policy requirement to avoid exposing private libs globally. |
The text was updated successfully, but these errors were encountered: