<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 05/30/2014 12:11 PM, Sylvain Joyeux
wrote:<br>
</div>
<blockquote
cite="mid:CAKDpF4SNr438UkbACEEOco-=2q3k-3KEDmkbwpGfzBCZrMHiTw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Current State</div>
<div>-------------------</div>
I've migrated rock.base and rock.toolchain to github,
integrating them into a 'rock.core' package set, adding as some
other "core" packages.
<div>
<br>
</div>
<div>I've updated the build configuration and package sets, and
put the updated configurations on github as well in order to
not disrupt the current installations "until it is ready"</div>
<div><br>
</div>
<div>It means, in practice, that one can bootstrap a
github-based build using</div>
<div> <a moz-do-not-send="true"
href="http://github.com/rock-core/buildconf">http://github.com/rock-core/buildconf</a></div>
<div><br>
</div>
<div>and <a moz-do-not-send="true"
href="https://github.com/rock-core/buildconf/raw/master/bootstrap.sh">https://github.com/rock-core/buildconf/raw/master/bootstrap.sh</a></div>
<div><br>
</div>
<div>What is left to be done</div>
<div>-----------------------</div>
<div> - one question: should not we split the rock package set
into subprojects as well (for me, it is +1, it would make more
sense from a management point of view to have a package and
its package set in the same organization)</div>
</div>
</blockquote>
<br>
Does it mean that it will be organized as it is in gitorious?
Meaning:<br>
rock.core (now it's rock.base + rock.toolchain + rock.gui + some
drivers like transformer, frame-helper and few more)<br>
rock.slam<br>
rock.drivers<br>
rock.control<br>
rock.planning<br>
rock.tutorials<br>
...<br>
<br>
<blockquote
cite="mid:CAKDpF4SNr438UkbACEEOco-=2q3k-3KEDmkbwpGfzBCZrMHiTw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div> - one thing to do: re-create the rock.base and
rock.toolchain metapackages in rock.core to ensure smooth
migration from the existing buildconfs</div>
</div>
</blockquote>
<br>
Question: Would the new rock package set have an impact in the
folder structure? Meaning frame-helper will be located into
./core/frame-helper instead of the current
./image-processing/frame-helper or perhaps
./core/image-processing/frame-helper<br>
<br>
Since there is already a kind of renaming during the migration
(e.g.: rock.core). Question: Do we what to rename some rock package
set (i.e: it would make more sense to have one called
rock.perception which could be the current rock.image-processing +
image stitching + pcl related stuffs, + future things ...) for me it
is +1<br>
<br>
Javier.
<blockquote
cite="mid:CAKDpF4SNr438UkbACEEOco-=2q3k-3KEDmkbwpGfzBCZrMHiTw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div> - testing</div>
<div> - update the gitorious package sets (that everyone is
currently using) to auto-import rock-core and the github-based
rock package set.</div>
<div><br>
</div>
<div>Sylvain</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Rock-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Rock-dev@dfki.de">Rock-dev@dfki.de</a>
<a class="moz-txt-link-freetext" href="http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev">http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev</a>
</pre>
</blockquote>
<br>
<br>
</body>
</html>