On 10/17/07, Andy Feldman <[EMAIL PROTECTED]> wrote: > On 10/16/07, Leandro Motta Barros <[EMAIL PROTECTED]> wrote: > > So, is this a bug or I am supposed to run > > Compile as superuser only? > > I had to fix those permissions in 013 as well. It's not the only bug in > running Compile as a normal user: if the Recipe defines any pre_ or post_ > functions that modify the target installation directory under /Programs (or > anything else, really) you'll see permissions errors and have to call Compile > again as superuser. Generally, though, it works.
Thanks for the analysis, it's good to pinpoint those failure points. In a future version of Compile, I want the hook (pre_/post_) functions to run sandboxed (not now as that would break some(/many?) recipes). This will also allow to sudo the calls as needed. > On Wednesday 17 October 2007 18:27, Hisham Muhammad wrote: > > As for me, I usually just run it as > > superuser. > > Any particular reason? It seems most of the devs do this, despite having all > the Sudo calls in the scripts. To be honest, "laziness", mostly. When I'm in a hurry to fix some bug or get something to work it's usually quicker to use sudo than to divert my focus and go through Compile and try to figure out what's wrong. That said, any fixes/patches to improve non-superuser support is welcome. -- Hisham _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
