Bug 51646 – env-update mis-separates CONFIG_PROTECT in /etc/csh.env

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description splite 2004-05-21 07:17:43 UTC]

env-update generates colon-separated CONFIG_PROTECT and CONFIG_PROTECT_MASK variables for /etc/csh.env when they should be space-separated.  The bug is obvious by inspection:  the csh.env generation code lacks the check for CONFIG_PROTECT etc. that the /etc/profile code has.  Patch is attached.  (Patch also corrects the spelling of "separated".  Remember, there's A RAT in sepARATe.)
Marking as critical as emerge could clobber files that should be protected if root's shell is csh.

Reproducible: Always
Steps to Reproduce:
1. % env-update
2. % grep CONFIG_PROTECT /etc/csh.env
3. Wonder if I'm the Gentoo-er who uses csh.

Actual Results:  
% grep CONFIG_PROTECT /etc/csh.env
setenv CONFIG_PROTECT
'/usr/X11R6/lib/X11/xkb:/usr/kde/3.1/share/config:/usr/share/texmf/tex/generic/config/
/usr/share/texmf/tex/platex/config/:/usr/share/config'

Expected Results:  
% grep CONFIG_PROTECT /etc/csh.env
setenv CONFIG_PROTECT '/usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/
/usr/share/config'

[Comment 1 splite 2004-05-21 07:19:41 UTC]

Created attachment 31793 [details, diff]
patch to portage.py to fix CONFIG_PROTECT generation for /etc/csh.env

[Comment 2 Masatomo Nakano (RETIRED) 2004-06-20 00:03:02 UTC]

Fixed in CVS.

[Comment 3 Nicholas Jones (RETIRED) 2004-10-22 08:47:35 UTC]

Bug has been fixed and released in stable portages on or before 2.0.51-r2