<br><br><div class="gmail_quote">On Thu, Jan 13, 2011 at 5:15 PM, Tim Niemueller <span dir="ltr"><<a href="mailto:tim@niemueller.de">tim@niemueller.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On 13.01.2011 23:12, Hedayat Vatankhah wrote:<br>
> In anaconda package customization UI, the left column shows categories<br>
> (Desktop Environment, Applications, Server ...) and the right column<br>
> shows groups of the selected category.<br>
> Package groups are organized in comps.xml itself, so there is no need to<br>
> change anything in the packages themselves.<br>
<br>
</div>Ok, Rich, which category is the Robotics Suite in?<br>
<br>
The package group was just mixed in, I want to propose a package group<br>
specific to robot software, we have quite a few packages to which this<br>
could apply.<br>
<div><div></div><div class="h5"><br>
Tim<br>
<br></div></div></blockquote><div><br>I think we fit best in the Development category. I'm creating a new group inside of the development category for our packages, called Robotics Suite, which will contain the robotics related stuff. I'm just not sure whether or not it makes more sense to list the -devel packages or the base packages for our stuff (or both). For instance, should I include player-devel and/or player? mrpt-devel and/or mrpt? I'm leaning towards including devel packages instead of base ones, since tutorials will probably rely on them at some point.<br>
<br>Rich<br></div></div>