-
Notifications
You must be signed in to change notification settings - Fork 102
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
Depend on libconsole-bridge-dev instead of rosconsole? #81
Comments
Not sure if that effects the decision / implementation. One question will be where |
Interesting— yeah, not having an actual TU to put that in does muddy the waters a bit. However, given the context here, perhaps it would be reasonable to just do it once as a heap-allocated thing when the first ClassLoader is initialized. Anyway, would have to play with it a bit. |
My preference here is to wait for |
Since I don't think we are ever going to split |
We desire to introduce
pluginlib
as a dependency for packages insideros_comm
without creating a repo-level circular dependency, which would presently be the case on account ofrosconsole
being insideros_comm
(see ros/ros_comm#1206).An obvious solution is to extract
rosconsole
into its own repo, but I wonder about breaking the dependency on this end, too. Excluding tests, all usages of logging in this repo are as follows:The main issue with switching this is that console_bridge doesn't have the concept of named loggers the way rosconsole does, so that would be lost, however it seems like there may be some logic within rosconsole_bridge that attempts to recover a prefix embedded in the log string itself:
https://github.com/ros/rosconsole_bridge/blob/8e27f6ef86c84b78d9fd20d883923fca70ba3532/src/bridge.cpp#L56-L75
Would a PR that switches this over be acceptable to the maintainers?
The text was updated successfully, but these errors were encountered: