Hi,

I am hitting the same problem about the gui dependency in rock.core now and would like to reopen that discussion again:

Am 04.07.2014 09:32, schrieb Sylvain Joyeux:
On Fri, Jul 4, 2014 at 9:29 AM, Matthias Goldhoorn <
[email protected]> wrote:

  So what's the best way to solve this?

Create a rock.core.nogui metapackage. Make it a duplicate of the rock.core
metapackage, but without the GUI packages.

Wouldn't it be better to have it the other way around?
There should be one metapackage containing only the necessary packages to have the robot running and have additional metapackages for gui and simulation.

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?

Regards,
Christian

Sylvain



_______________________________________________
Rock-dev mailing list
[email protected]
http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev


--
 Christian Rauch
 Space Robotics

 Universität Bremen
 FB 3 - Mathematik und Informatik
 AG Robotik
 Robert-Hooke-Straße 1
 28359 Bremen, Germany

 Zentrale: +49 421 178 45-6611

 Besuchsadresse der Nebengeschäftstelle:
 Robert-Hooke-Straße 5
 28359 Bremen, Germany

 Tel:     +49 421 178 45-6619
 Empfang: +49 421 178 45-6600
 Fax:     +49 421 178 45-4150
 E-Mail:  [email protected]

 Weitere Informationen: http://www.informatik.uni-bremen.de/robotik


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
Rock-dev mailing list
[email protected]
http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev

Reply via email to