<div dir="ltr">I've written up a tutorial on how to install indigo in a chroot on ubuntu 13.04 and compile ros packages: <a href="http://wiki.ros.org/ROS/Tutorials/InstallingIndigoInChroot">http://wiki.ros.org/ROS/Tutorials/InstallingIndigoInChroot</a><div>
<br></div><div>It works for me on 13.04; fixes are welcome!</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Mar 28, 2014 at 3:00 PM, Jon Binney <span dir="ltr"><<a href="mailto:jon.binney@gmail.com" target="_blank">jon.binney@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Yeah, the system dependencies such as gazebo would definitely be problematic, so I understand if it isn't feasible. Maybe worth coming up with a quick list of what system dependencies have problematic version changes between precise and trusty, to gauge the difficulty of this approach?</div>
<div class="HOEnZb"><div class="h5">
<div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Mar 28, 2014 at 12:05 PM, William Woodall <span dir="ltr"><<a href="mailto:william@osrfoundation.org" target="_blank">william@osrfoundation.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>On Thu, Mar 27, 2014 at 4:36 PM, Jon Binney <span dir="ltr"><<a href="mailto:jon.binney@gmail.com" target="_blank">jon.binney@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
As has already been identified in this thread, building Hydro from<br>
source on other systems (Ubuntu Saucy, Ubuntu Trusty) currently works<br>
quite smoothly, with the caveat being the ~30 minute build time for<br>
Hydro-desktop, which is of course dependent on one's internet<br>
bandwidth and system performance.<br></blockquote><div><br></div></div><div>If it builds from source on other platforms, would there still be significant developer effort to create debs? Or do you mean that only the core packages in hydro build from source on Saucy/Trusty?</div>
<div><br></div><div>The ideal situation from a developer point of view would be if there were indigo debs for ubuntu precise. This would allow people who are running hydro/precise to update their own packages so that they work with indigo, and then to install ubuntu trusty on their machines. It would be essentially the same as when we switched from electric to fuerte - fuerte had debs on lucid, but also had debs for precise.</div>
</div></div></div></blockquote><div><br></div></div><div>Generally any time you port forward (add debs for a new ubuntu for an existing ROS distro) or backwards (create debs for a new ROS distro on ubuntu platforms that are older or unsupported), there is going to be some significant work involved.</div>
<div><br></div><div>However, we are not as far along in the Indigo first time releases, so having bloom start to make debian files for Indigo on Precise is tractable, but still a lot of work to re-bloom already released things. The other problem with backporting Indigo to precise is the changes in dependencies. This is not generally a problem with things like boost or log4cxx, but in this case Gazebo is a good example of a problem. Gazebo's default in precise is 1.x and in trusty it is 2.x, so now any ROS packages which should be released into Indigo not only need to update for 2.x Gazebo, but also needs to be backwards compatible with Gazebo 1.x. To avoid that, you could install the gazebo2 deb on precise for Indigo, but I believe (could be wrong) that the gazebo2 deb cannot be installed at the same time as the gazebo1 deb, so then you wouldn't be able to have Indigo above gazebo and Hydro above gazebo installed at the same time.</div>
<div><br></div><div>Gazebo is just an example, and while there are solutions to these problems, they always take effort, not just for us but for maintainers.</div><div><br></div><div>Unlike Hydro on Trusty, I believe Indigo on Precise is tractable, but still a big cost in terms of engineering time.</div>
<div><div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div><br></div><div>That being said, I understand that it's a huge effort to support extra distributions, so this may not be practical.</div><span><font color="#888888"><div><br></div><div>-Jon</div></font></span><div>
<div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Taking these considerations into account, we think the best approach<br>
is to improve the experience of building ROS distributions from<br>
source, so they can be used more easily on distros for which they were<br>
not originally targeted. There are various things that could be done<br>
to improve the build-from-source process: better/easier documentation<br>
[1], better/easier software tools to automate the process [2], and so<br>
on. If you are interested in participating, ros-sig-buildsystem [3]<br>
would be a good place for such documentation/tool development and<br>
discussion.<br>
<br>
Cheers,<br>
Morgan<br>
<br>
[1] <a href="http://wiki.ros.org/hydro/Installation/Source" target="_blank">http://wiki.ros.org/hydro/Installation/Source</a><br>
[2] perhaps the tools could display cat photos in ASCII art during the build.<br>
[3] <a href="https://groups.google.com/forum/#!forum/ros-sig-buildsystem" target="_blank">https://groups.google.com/forum/#!forum/ros-sig-buildsystem</a><br>
<div><div><br>
On Thu, Mar 27, 2014 at 11:19 AM, Jochen Sprickerhof<br>
<<a href="mailto:ros-users@jochen.sprickerhof.de" target="_blank">ros-users@jochen.sprickerhof.de</a>> wrote:<br>
> * Michael Fritscher <<a href="mailto:michael.fritscher@telematik-zentrum.de" target="_blank">michael.fritscher@telematik-zentrum.de</a>> [2014-03-27 18:08]:<br>
>> But in my experience, apt can handle about every kind of abuse fairly well -<br>
>> to be honest I've done way trickier things in the past without any problems.<br>
><br>
> Yes, I did these tricks myself aswell. But as Jack wrote, we should not<br>
> propose it as the official way, as it's too fragile to maintain in<br>
> larger installations. But if you want to do it cleanly, use a chroot<br>
> (have a look at the schroot package), this is what I use nowadays.<br>
><br>
> Cheers Jochen<br>
><br>
</div></div><div><div>> _______________________________________________<br>
> ros-users mailing list<br>
> <a href="mailto:ros-users@lists.ros.org" target="_blank">ros-users@lists.ros.org</a><br>
> <a href="http://lists.ros.org/mailman/listinfo/ros-users" target="_blank">http://lists.ros.org/mailman/listinfo/ros-users</a><br>
><br>
_______________________________________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@lists.ros.org" target="_blank">ros-users@lists.ros.org</a><br>
<a href="http://lists.ros.org/mailman/listinfo/ros-users" target="_blank">http://lists.ros.org/mailman/listinfo/ros-users</a><br>
</div></div></blockquote></div></div></div><br></div></div>
<br>_______________________________________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@lists.ros.org" target="_blank">ros-users@lists.ros.org</a><br>
<a href="http://lists.ros.org/mailman/listinfo/ros-users" target="_blank">http://lists.ros.org/mailman/listinfo/ros-users</a><br>
<br></blockquote></div></div></div><span><font color="#888888"><br><br clear="all"><div><br></div>-- <br>William Woodall<div>ROS Development Team</div><div><a href="mailto:william@osrfoundation.org" target="_blank">william@osrfoundation.org</a></div>
<div><a href="http://williamjwoodall.com/" target="_blank">http://williamjwoodall.com/</a></div>
</font></span></div></div>
<br>_______________________________________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@lists.ros.org" target="_blank">ros-users@lists.ros.org</a><br>
<a href="http://lists.ros.org/mailman/listinfo/ros-users" target="_blank">http://lists.ros.org/mailman/listinfo/ros-users</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>