On Fri, 12 Jan 2007 10:53:02 +0100 Harald van Dijk <[EMAIL PROTECTED]> wrote: | On Fri, Jan 12, 2007 at 08:30:49AM +0000, Ciaran McCreesh wrote: | > On Fri, 12 Jan 2007 09:11:11 +0100 Harald van Dijk | > <[EMAIL PROTECTED]> wrote: | > But ebuilds setting RESTRICT=userpriv are explicitly saying "we | > can't use userpriv not because of an accident but because the build | > system really needs elevated privs". If a user wants to be | > protected against accidental mistakes, they set FEATURES=userpriv | > and accidental mistakes are caught whilst intentional requirements | > are let through. | | Accidental mistakes in packages for which the ebuilds specify | RESTRICT=userpriv are also let through.
Which is why a) developers check userpriv restricted packages much more carefully and b) there are other additional safety measures in place. | ACCEPT_RESTRICT=-userpriv (or whatever) would mean "I want to be | protected against accidental mistakes, even if it means I can't | install some software." Which is a silly and arbitrary distinction to make, and users should not be encouraged to do so. -- Ciaran McCreesh Mail : ciaranm at ciaranm.org Web : http://ciaranm.org/ Paludis, the secure package manager : http://paludis.pioto.org/
signature.asc
Description: PGP signature
