This concerns the following ebuilds: net-libs/ignition-msgs net-libs/ignition-transport sci-libs/ignition-math (as far as I can tell right now) The code looks like it should be slottable because everything is suffixed with the major version, but upstream does some weird hackery in the cmake find_package logic that breaks it. I guess it could be fixed, but I grow tired of cleaning up after all these messy robotics devs. There's probably no point in installing multiple versions of any of these, anyways, so let's just unslot everything. I also doubt that anything other than Gazebo and its relatives will ever depend on these. I guess in theory someone might want to have a slotted gazebo, but as long as there's no real need for that, there's also no need to slot its dependencies. Reproducible: Always
the point of slotting here is not to allow multiple installs: this is, as you correctly noted, mostly pointless the point is to be able to :SLOT depend on those packages because if a package uses ign-msgs:2 it will never work with ign-msgs3 due to the renaming in all the files
> the point is to be able to :SLOT depend on those packages because if a > package uses ign-msgs:2 it will never work with ign-msgs3 due to the > renaming in all the files Right, that makes sense. However in that case, it might be a good idea to have the slots mutually block each other, because the way upstream has implemented it currently, they can't be installed alongside each other. I.e. there are no file collisions, but the various cmake find-scripts won't find anything any more if more than one slot is installed.
(In reply to Victor Mataré from comment #2) > > the point is to be able to :SLOT depend on those packages because if a > > package uses ign-msgs:2 it will never work with ign-msgs3 due to the > > renaming in all the files > > Right, that makes sense. However in that case, it might be a good idea to > have the slots mutually block each other, because the way upstream has > implemented it currently, they can't be installed alongside each other. I.e. > there are no file collisions, but the various cmake find-scripts won't find > anything any more if more than one slot is installed. I'm in the process of updating those and didn't see any problem with multiple slots installed
