-
Notifications
You must be signed in to change notification settings - Fork 36
catkinization? #4
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
Comments
As I'm currently catkinizin the knowrob_addons packages and some of them depend on this, I'm in favour of catkinizing it. However, I'd also recommend to refactor this package in order to separate the Gazebo parts from the URDF parts and the OWL description in order to avoid an explosion of dependencies. |
OK. Catkinization it is, then! Refactoring also sounds good. This is already a single repo, and we could split it in place.. Shall we sit together and make a list of TODOs? Update:
|
@fairlight1337 : What do you think regarding this? Would you agree with splitting up this package? How about the Gazebo files, are they still up to date? |
Hey, I didn't know the URDF parts were still in the repo. I thought I remove them at some point, but if they are there, I think you can safely split that. They aren't necessary for the robot specific stuff we're doing. So, all in favor of the above!
|
Updates: CRAM can still load the semantic map from the updated KnowRob + iai_maps, launched using the 'json.launch' file in iai_maps, as before. I've created a tag 'rosbuild' in case you'd like to go back to the old version. So I'd propose to merge the pull request and either switch to the 'rosbuild' tag or the new KnowRob. What do you think? |
All in favour of merging. Any other objections? |
Is there anything open left in this issue? |
Fixedi in 2f29098. |
This is still a rosbuild package. Does it make sense to catkinize this? It looks like it's build some prolog code and depends on a package ias_knowledge base. So I cannot really judge what's going on and the state..
The text was updated successfully, but these errors were encountered: