On 07/08/2014 01:53 PM, Sylvain Joyeux wrote:
I don't like this, as in most situations people *want* the GUI. The
nogui case is a special case. all packages including the GUI is the
common case. Note that gui/vizkit was already part of rock.toolchain
before the migration.
the embedded guys don't want to have anything to do with gui-stuff. In
my view: keep the minimal depedency-chain as short as possible.
otherwise people will start talking using words like "bloated"
Moreover, rock.simulation is not part of rock.core, and should IMO not be.
Finally: in principle, one should not *have* to use rock.core on a
"finalized" system (such as a robot) as he can enumerate the packages
he needs instead of selecting rock.core. Since we are talking about
having e.g. a robot, it would IMO be a better approach as it ensures
that, on the headless system, there are only packages that are useful.
so no gui-dependency in central packages?
E.g. a package rock.core itself should not depend on gui packages,
but should contain the toolchain and drivers. Two additional
metapackages rock.gui and rock.simulation should depend on
rock.core and add their additional packages.
Suggestions?
+1
martin
_______________________________________________
Rock-dev mailing list
[email protected]
http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
