| 1 |
On 11/4/19 10:50 AM, Joakim Tjernlund wrote: |
| 2 |
> On Mon, 2019-11-04 at 18:35 +0000, Joakim Tjernlund wrote: |
| 3 |
>> |
| 4 |
>> I have a profile.bashrc in my profile where I try to set INSTALL_MASK: |
| 5 |
>> |
| 6 |
>> cat profile.bashrc |
| 7 |
>> INSTALL_MASK="${INSTALL_MASK} $(. $(dirname "$*")/etc_file_list)" |
| 8 |
>> export INSTALL_MASK |
| 9 |
>> echo "profile INSTALL_MASK: ${INSTALL_MASK}" |
| 10 |
>> |
| 11 |
>> PKG_INSTALL_MASK="${PKG_INSTALL_MASK} ${INSTALL_MASK}" |
| 12 |
>> export PKG_INSTALL_MASK |
| 13 |
>> echo "profile PKG_INSTALL_MASK: ${PKG_INSTALL_MASK}" |
| 14 |
>> |
| 15 |
>> Using portageq envvar INSTALL_MASK I expect to see my settings but |
| 16 |
>> INSTALL_MASK is empty. |
| 17 |
>> |
| 18 |
>> Am I missing something ? |
| 19 |
>> |
| 20 |
>> Jocke |
| 21 |
> |
| 22 |
> in profile make.defaults I have |
| 23 |
> CONFIG_PROTECT="" |
| 24 |
> yet I see: |
| 25 |
> portageq envvar CONFIG_PROTECT |
| 26 |
> /etc |
| 27 |
> |
| 28 |
> Is portageq envvar somewhat broken? |
| 29 |
> |
| 30 |
|
| 31 |
Well, it's complicated because CONFIG_PROTECT is an "incremental" |
| 32 |
variable. You can try to clear it out completely by setting |
| 33 |
CONFIG_PROTECT="-*" in profile make.defaults, but that only works if the |
| 34 |
CONFIG_PROTECT="/etc" setting came from earlier in the inheritance |
| 35 |
hierarchy. You can use this command to see the inheritance order: |
| 36 |
|
| 37 |
python -c 'import portage; print("\n".join(portage.settings.profiles))' |
| 38 |
-- |
| 39 |
Thanks, |
| 40 |
Zac |
Archives