Create metapackage

[cdondrup]

Just for convenience, could this repo get a meta package which is added to one of the more general packages in metapackages?

[gestom]

no clue

[marc-hanheide]

I like the honest self-assessment 😄

Look at https://github.com/strands-project/strands_perception_people/tree/indigo-devel/strands_perception_people

What @cdondrup means is to create a package named "fremen" that is run_depend on all the fremen packages, but doesn't contain anything else, but is flagged as a metapackae in package.xml and CMakeLists.txt, like package.xml and CMakeLists.txt

[gestom]

Would need to resolve some circular dependencies. We have to wait for Bruno to start using FremenServer and not frenap for topological predictions. (In progress since last week).

[marc-hanheide]

circular dependencies? This should be a top-level package that just subsumes all the packages in this repo. That shouldn't introduce any circulars?

[marc-hanheide]

but, yes, it's not urgent.

[cdondrup]

Thing is that one of the packages in this repo depends on strands navigation and strands navigation depends on a different package in this repo. Therefore there is circular dependency between the fremen and strands_navigation repo. By creating a meta package and adding it to strands_desktop for example, Jenkins would fail to build due to this circular dependency. Therefore the actual meta package is not the cause but the reason Jenkins wouldn't be able to build it any more.

[marc-hanheide]

OK. So those dependencies need to be resolved. Usually by putting things in a _msgs package.

[marc-hanheide]

Has anyone done anything about this?

[gestom]

We thought it would be better to solve the problem with model bias in exploration/exploitation scenarios. If our current solution of that works OK during the next pre-deployment, we could cleanup the fremen-related code and wrap the packege after IROS deadlines.