On Wednesday 09 December 2009 21:31:33 Hans-Peter Jansen wrote:
On Wednesday 09 December 2009, 19:17:44 Rüdiger Meier wrote:
The main problem is that I'm not root or rather don't want to do that as root on our production systems.
Did you noticed this paragraph:
<cite> If you start the build as normal user (good idea!), you will be asked for the root password of your local machine. You can avoid that if you add your user to /etc/sudoers and edit your ~/.oscrc : su-wrapper = sudo
and with visudo add the line (as root): <your login name> ALL = NOPASSWD: /usr/bin/build </cite>
Jup, but I watched the script "/usr/bin/build" and think I should not run it as root on a machine which is productively used for something important. There is IMO a risk (which I can't yet clearly see) that some Makefile or whatever could run amok somehow. This is probably no risk unless I would set BUILD_ROOT="/". But moreover I see "/usr/bin/build" is using most commands without absolute paths which is dangerous. If "/usr/bin/build" would be safe to give that sudo permissions to an evil user when I would use it too without doubt. But no prob - I will use rpmbuild for local testing (like I did before knowing that nice osc) and opensuse build farm (or a dedicated build machine) for deterministic chrooted builds.
Is it a problem to ask your admin for these simple mods? I'm the admin :)
How do you manage to install the built rpms? Good point, of course I do with root permissions. Before installing non-official-packages I view at least the filelist and pre/post install scripts which usually does not take much time (in contrast to %build and %install section).
cu, Rudi -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org