Please approve flavorization of ignition-* ports

[yuri]

Summary

Ignition robotics framework allows to install individual packages simultaneously in different versions.The top app that uses the ignition framework will be 'gazebo'.

[tobik]

This seems like an abuse of flavors. Flavors are for building different variants of a single version, not multiple different versions.

How would patch files work with multiple flavors in play?

devel/ignition-cmake/Makefile

30–31

.elif or just .else

devel/ignition-common/Makefile

42–43

.elif ?

48–49

.elif or just .else

devel/ignition-msgs/Makefile

34–35

.elif ?

devel/ignition-transport/Makefile

41–42

.elif or just .else

math/ignition-math/Makefile

32–33

.elif or just .else

43–44

CMAKE_ON= CMAKE_DISABLE_FIND_PACKAGE_SWIG

misc/sdformat/Makefile

39–40

.elif or just .else

[yuri]

In D18293#387998, @tobik wrote:

This seems like an abuse of flavors. Flavors are for building different variants of a single version, not multiple different versions.

They chose to manage versions this way. It's better to contain them as flavors vs. to generate a lot of separate port directories.

How would patch files work with multiple flavors in play?

Patches are in individual patch directories (files-vN/).

[tobik]

In D18293#388008, @yuri wrote:

Patches are in individual patch directories (files-vN/).

Ah ok, I somehow missed that PATCHDIR was set for this in a couple of ports.

[mat]

No on flavors which produce different versions of the software.