[Rock-dev] rock-create-orogen usage

[Janosch Machowinski]

I don't think this a good idea.
If one adds operations or anything that changes the
template afterwards the templates need to be copied
by hand. This actually de-streamlines the process.
Also it is annoying in the case that one need a different
task name as one needs to delete the files in this case.

For the git problem, create a correct .gitignore that
ignores all files that should not end up in the git.
Greetings
     Janosch

On 19.03.2013 12:15, Sylvain Joyeux wrote:
> So far, rock-create-orogen was not running orogen. The reason being that
> we wanted to allow the user to change the project and/or the task name.
> However, it makes the creation of oroGen projects less straightforward
> than they could be.
>
> Since the default "Task" name for the task context *is* the convention
> and covers 99% of all the cases, I would like to change that: i.e. have
> rock-create-orogen actually run orogen.
>
> An added benefit would be that we could create the proper git. Usually,
> people do not add all the files that should be in the git (because it is
> hard to know which should be) and then we get a git problem when we do
> add the files later on.
>
> Anyone against ?
>


-- 
  Dipl. Inf. Janosch Machowinski
  SAR- & Sicherheitsrobotik

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

  Tel.:     +49 421 178 45-6614
  Zentrale: +49 421 178 45-6611
  Fax:      +49 421 178 45-4150
  E-Mail:   jmachowinski at informatik.uni-bremen.de

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