<div class="gmail_quote">On Wed, Feb 11, 2009 at 10:59, Phillip Warner <span dir="ltr"><<a href="mailto:pc_warner@yahoo.com">pc_warner@yahoo.com</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;">
<div class="Ih2E3d">--- On Tue, 2/10/09, Chess Griffin <<a href="mailto:chess@chessgriffin.com">chess@chessgriffin.com</a>> wrote:<br>
<br>
> So, the question is: how many people feel strongly about<br>
> keeping the<br>
> ability to run sbopkg as a non-root user? Could folks<br>
> adapt to using<br>
> sbopkg only as root?<br>
<br>
</div>ROOT-only sounds fine to me. The main use of a non-root user for me would be for testing SlackBuilds, and I don't have to use sbopkg for this (though root could drop perms as mentioned in a feature request).<br>
<br>
Non-root users really only need to view the Changelog and search/browse the repo. Non-admins could just use links/lynx on SBo if they need this from their console ;)<br>
<font color="#888888"></font></blockquote><div><br>So, is there any possiblity that seperate the script into two, one requered root permission(install/upgrade/remove pkg etc.), one doesn't need(rsync local repository, search/brows installed pkg etc.). This way can avoid a root own huge local repository and convienent for daily use.<br>
</div></div><br>-- <br>Cheers,<br>Grissiom<br>