hi, i wonder why sudo is used in Compile in the newest release because sudo Compile progX did fine for me.
i dont get the point of using sudo too. -> some comments follow On Fri, 2008-05-09 at 23:24 +0200, Daniele Maccari wrote: > Lucas C. Villa Real wrote: > > On Fri, May 9, 2008 at 4:16 PM, Daniele Maccari <[EMAIL PROTECTED]> wrote: > > > >> Ok, I finally solved the problem (if right or wrong, I don't know). > >> Attached > >> you'll find the patch, please let me know. > >> This way files on which current user has no permissions should be correctly > >> managed, as well as globbing (which sudo prevents from working, since the > >> command is first parsed by shell, and the permission problem arises). > >> > > > > Dude, this $sudo_exec thing is becoming ridiculous. Maintaining > > Scripts and Compile *used* to be a simple thing. What's wrong with > > requiring superuser access to launch Compile? especially if all recipes need attention again, and using recipes to fix permission problems just makes no sense?! > > > > > To be honest, I don't really know. The most annoying issues, in my > opinion, would be the fact that all /F/C entries would be gobo:sys > owned, nothing more. > If we can find a solution to this I'd have no problems in dropping sudo. whats the problem with havin /F/C being superuser only? users should have a ~/.Compile or something to do the thing right, letting the user write to /F/C can raise security issues... > _______________________________________________ > gobolinux-devel mailing list > gobolinux-devel@lists.gobolinux.org > http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel -- MOSAIK Software - Christian Holzberger Web: http://www.mosaik-software.de _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
