Re: [gentoo-dev] Proposal of "uncooperative-root" in SUPPORTED_FEATURES

2014-07-04 Thread Joshua Kinard
On 07/04/2014 14:11, Rick "Zero_Chaos" Farina wrote: > On 07/04/2014 12:25 PM, dREPLACEeLETTEReEjBYeLETTEReAatGMA ILcom wrote: > > It is incredibly hard to seriously review anything with this from email > address. > > -Zero > > >> Hello to all, > >> Summary: I have made many mods to sys-app/po

Re: [gentoo-dev] Proposal of "uncooperative-root" in SUPPORTED_FEATURES

2014-07-04 Thread Rick "Zero_Chaos" Farina
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/04/2014 12:25 PM, dREPLACEeLETTEReEjBYeLETTEReAatGMA ILcom wrote: It is incredibly hard to seriously review anything with this from email address. - -Zero > Hello to all, > > Summary: I have made many mods to sys-app/portage (2013 version).

[gentoo-dev] Proposal of "uncooperative-root" in SUPPORTED_FEATURES

2014-07-04 Thread dREPLACEeLETTEReEjBYeLETTEReAatGMA ILcom
Hello to all, Summary: I have made many mods to sys-app/portage (2013 version). The result is a proposal of patch for latest sys-app/portage, see below. Main result of my mods to gentoo prefix: FEATURES=uncooperative-root emerge -bv =firefox-17 now works on EPREFIX on Android-4.1 ARM. I use n

Re: [gentoo-dev] Standardise the variable for including eclasses only once

2014-07-04 Thread Michał Górny
Dnia 2014-07-04, o godz. 11:26:01 Ulrich Mueller napisał(a): > Since names like _USER or _PAM look a little dangerous, I suggest > __ECLASS for the variable's name. > > I have no strong preference for the variable's value. Is testing for > a non-empty value sufficient? Then we should assign some

[gentoo-dev] Standardise the variable for including eclasses only once

2014-07-04 Thread Ulrich Mueller
Hi all, Several of our eclasses use a mechanism that prevents them from being inherited more than once. Some eclasses test for a special value [1]: ___ECLASS_ONCE_EUTILS="recur -_+^+_- spank" while others simply assign 1 and test for a non-empty variable [2]: _GIT_R3=1 The problem with th