<div class="gmail_quote">On Wed, Feb 11, 2009 at 11:39 AM, Serban Udrea <span dir="ltr"><<a href="mailto:serban.udrea@skmail.ikp.physik.tu-darmstadt.de" target="_blank">serban.udrea@skmail.ikp.physik.tu-darmstadt.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hello!</blockquote><div> </div><div>Hello! <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I dare to disagree with other posters.I actually do not understand why anything else but installing the final package needs root rights. I am (still) working on some packages I hope to submit soon and I do everything but package installation/removal as a normal user without problems. Thus I would actually drop root for anything but final installation/removal. In my opinion it is always good to use root rights as sparingly as possible.<br>
<br>
I do not know how big a problem is to change sbopkg, such that just the last step needs root rights, but I would say that a first change would be to have sbopkg default directories with access rights like /tmp.</blockquote>
<div><br>There are two ways of thinking "user-mode" support:<br>- one is to allow normal users to do what a normal user can (like browsing the package repository), but not allowing root-only operations (e.g. removing some options from the menus) -- this is what we currently have in sbopkg;<br>
- the other is to always show all the operations, asking the root password for those which are admin-only -- this is what you're talking about.<br><br>The first option is something that clutters the code and brings very little advantages, thus Chess' proposal to remove it.<br>
<br>Your approach would need to be implemented from scratch, as there's currently nothing like that in sbopkg. That would require at least the usage of fakeroot (which is unsupported by the SBo admins and therefore a possible source of problems) and the admin should set up sudo and use directories with proper access permissions (the security-aware defaults aren't likely to change).<br>
This can happen at some point in the future. But don't expect it to happen tomorrow ;-)<br><br>Thank you for daring to disagree!<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div>
</div></div></blockquote></div><br>Regards<br>-- <br>Mauro Giachero<br>