See the prefs.json I pasted, just add that property to your (or create one like that if you don't have a prefs.json).<span></span><br><br>On Thursday, 11 July 2013, Gonzalo Odiard wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Sorry, what is the procedure to enable/disable the use of chroot?<div><br></div><div>Gonzalo</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jul 11, 2013 at 11:26 AM, Daniel Narvaez <span dir="ltr"><<a href="javascript:_e({}, 'cvml', 'dwnarvaez@gmail.com');" target="_blank">dwnarvaez@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">This is now implemented<br><br>[dnarvaez@dnarvaez sugar-build]$ cat prefs.json <br>{"use_broot": false}<br>
</div><div class="gmail_extra"><div><div><br><br><div class="gmail_quote">On 10 July 2013 15:55, Daniel Narvaez <span dir="ltr"><<a href="javascript:_e({}, 'cvml', 'dwnarvaez@gmail.com');" target="_blank">dwnarvaez@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><div>Hi Daniel,<br><br></div>yup, I'm planning to keep a non chrooted build that you can enable in prejs.json. Automatic dependencies installation will only for work for the distro we are using in the chroot though, as you are suggesting. That won't require any additional config maintenance (and related automate testing).<br>
<br></div>I'll try to get this in before merging. <br></div><div class="gmail_extra"><div><div><br><br><div class="gmail_quote">On 10 July 2013 15:49, Daniel Drake <span dir="ltr"><<a href="javascript:_e({}, 'cvml', 'dsd@laptop.org');" target="_blank">dsd@laptop.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Wed, Jul 10, 2013 at 6:10 AM, Daniel Narvaez <<a href="javascript:_e({}, 'cvml', 'dwnarvaez@gmail.com');" target="_blank">dwnarvaez@gmail.com</a>> wrote:<br>
</div><div><div>> I'm planning to merge the chroot branch on master. Though, since it's a<br>
> major change, I'm trying to avoid disruption as much as possible.<br>
><br>
> As a first step, I'm switch the build infrastructure to use that branch.<br>
><br>
> I encourage people to switch to the branch too when they have a chance<br>
> (perhaps without throwing away the master build until they have a working<br>
> chroot build) and to report any issue they run into.<br>
<br>
</div></div>Just personal preference, but I would prefer to keep working in a<br>
non-chrooted environment. One less layer, one less thing to go wrong<br>
or offer some kind of irritation. Of course it is up to you if you<br>
want to support that, but I think it has value as it is much closer to<br>
the environment that Sugar will be deployed in. I would have no<br>
problem with you picking a lone distro/version where this works,<br>
perhaps matching what is run as a chroot on the other distros, i.e. in<br>
this case you could say "OK, no chroot, but only if you're running<br>
F19"<br>
<span><font color="#888888"><br>
Daniel<br>
</font></span></blockquote></div><br><br clear="all"><br></div></div><span><font color="#888888">-- <br>Daniel Narvaez<br>
</font></span></div>
</blockquote></div><br><br clear="all"><br></div></div><span><font color="#888888">-- <br>Daniel Narvaez<br>
</font></span></div>
<br>_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="javascript:_e({}, 'cvml', 'Sugar-devel@lists.sugarlabs.org');" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br></blockquote></div><br></div>
</blockquote><br><br>-- <br>Daniel Narvaez<br><br>