Open j-rivero opened 2 years ago
I think the gz-garden
metapackage should install all the -cli
packages
I think the
gz-garden
metapackage should install all the-cli
packages
https://github.com/gazebo-release/gz-garden-release/pull/16
I left the issue open since there are other open questions.
Is the remaining question which package should host the .yaml
and .rb
files? If so, can they live in the -cli
packages?
I've been putting the .yaml
and .rb
files in the non-dev packages per https://github.com/gazebo-tooling/release-tools/issues/529. I think it should not be required to install -dev
packages in order to run these command line tools (whether via ruby or CLI11). The -dev
packages bring in a lot more dependencies that are not really needed to run these tools.
What binary package should host the .yaml and .rb files that are part of gz submodules? Note that lib package should just contain the shared library, we don't want them in the -dev package and the -cli- package is most of the times not installed by default. In Debian the arch-independent files are typically using a -common package (see gazebo-common).
If the lib
packages are supposed to contain only the shared library, then moving them to the -cli
package makes sense to me. I believe the plan/hope is to transition to CLI11 for all our command line tools, so this will be a more permanent solution.
If the lib packages are supposed to contain only the shared library, then moving them to the -cli package makes sense to me. I believe the plan/hope is to transition to CLI11 for all our command line tools, so this will be a more permanent solution.
Does not sound bad to me. The only remaining question is: should the -cli-
packages be installed as a soft dependency + by default of the main "libgzfoo" package? of "libgzfoo-dev" packages? If we don't don't move the current Suggests
to Recommends
we probably need to update many of our package documentation.
Making it a Recommends
of libgzfoo
would be best, I think.
The modules supported by the
gz
(previoslyign
) tool (such asgui
,fuel
,service
,topic
,sdf
, ...) are provided by different binary packages, typically by the-dev
packages. Completely separated from this submodules we also have standalone binaries (built using cli11) that can run on their own providing some interaction aside fromgz
.As part of https://github.com/gazebo-tooling/release-tools/issues/529 I think that we have been moving some of the
gz
submodules out from the library packages-dev
into the-cli-
packages (which was proposed to host the standalone cli11 binaries). These changes also had the side effect of pulling some of them out of the default installation when someone install the library or the-dev
package or thegz-garden
metapackage, see https://github.com/gazebosim/garden-tutorial-party/issues/1978#issuecomment-1253746290.So I think that we need to resolve two different somehow linked problems:
-dev
package and the-cli-
package is most of the times not installed by default. In Debian the arch-independent files are typically using a-common
package (see gazebo-common).-cli-
packages that install the standalone executable (cli11 powered)? Should they be installed by default with the main lib package (hence useRecommends
)? What kind of dependency the meta-packagegz-$collection
should do with them?Note that for Debian:
Currently listed as
Suggests
:Listed as
Recommends
and installed by default:ruby installations in install files: