Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
On LS_COLORS.
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo Forums Feedback
View previous topic :: View next topic  
Author Message
Chiitoo
Administrator
Administrator


Joined: 28 Feb 2010
Posts: 2571
Location: Here and Away Again

PostPosted: Fri Nov 14, 2014 10:57 am    Post subject: Reply with quote

User: drardbeg
Topic: abi_x86_32 Multilib madness [Not as SOLVED as I thought]
Post: post 7269682
Reason: The LS_COLORS variable in the verbose emerge --info here seems to be triggering the wide-wide-forum feature, taking some quotes with it even!
_________________
Kindest of regardses.
Back to top
View user's profile Send private message
steveL
Watchman
Watchman


Joined: 13 Sep 2006
Posts: 5153
Location: The Peanut Gallery

PostPosted: Fri Nov 14, 2014 1:43 pm    Post subject: Reply with quote

Chiitoo wrote:
The LS_COLORS variable in the verbose emerge --info here seems to be triggering the wide-wide-forum feature

Just wanted to say that I think emerge should be filtering that variable out, along with some others that are probably a bit more contentious.

It's completely useless information-wise, and certainly shouldn't be used by make et al (or something is wrong.)
Back to top
View user's profile Send private message
Chiitoo
Administrator
Administrator


Joined: 28 Feb 2010
Posts: 2571
Location: Here and Away Again

PostPosted: Fri Nov 14, 2014 2:09 pm    Post subject: Reply with quote

steveL wrote:
Chiitoo wrote:
The LS_COLORS variable in the verbose emerge --info here seems to be triggering the wide-wide-forum feature

Just wanted to say that I think emerge should be filtering that variable out, along with some others that are probably a bit more contentious.

It's completely useless information-wise, and certainly shouldn't be used by make et al (or something is wrong.)

Well the user has EMERGE_DEFAULT_OPTS="-va" and did not disable it for the that info output (I did that mistake once for a bug report... oopsies!), so yes, Portage is definitely being verbose there but at least it's on purpose. ^^
_________________
Kindest of regardses.
Back to top
View user's profile Send private message
steveL
Watchman
Watchman


Joined: 13 Sep 2006
Posts: 5153
Location: The Peanut Gallery

PostPosted: Fri Nov 14, 2014 5:53 pm    Post subject: Reply with quote

Chiitoo wrote:
steveL wrote:
I think emerge should be filtering that variable out, along with some others that are probably a bit more contentious.

It's completely useless information-wise, and certainly shouldn't be used by make et al (or something is wrong.)

Well the user has EMERGE_DEFAULT_OPTS="-va" and did not disable it for the that info output (I did that mistake once for a bug report... oopsies!), so yes, Portage is definitely being verbose there but at least it's on purpose. ^^

It's not the verbosity, it's that emerge already filters out some variables, and this one is always way too big, and functionally useless. It just clogs up the environment bz2 (and incidentally makes it much more awkward to look at in some editors.)

Still I should just mention it to zac next time I'm bugging him about portage's behaviour ;)

Sorry for noise.
Back to top
View user's profile Send private message
desultory
Bodhisattva
Bodhisattva


Joined: 04 Nov 2005
Posts: 9410

PostPosted: Tue Nov 18, 2014 4:58 am    Post subject: Reply with quote

Split from the reports topic, in case anyone wanted to refer back to them.
Back to top
View user's profile Send private message
mv
Watchman
Watchman


Joined: 20 Apr 2005
Posts: 6747

PostPosted: Tue Nov 18, 2014 7:29 am    Post subject: Reply with quote

steveL wrote:
Still I should just mention it to zac next time I'm bugging him about portage's behaviour ;)

When you do, you might want to have a ready suggestion:
I am using since years the following "emerge" command (ordered in $PATH before emerge) which cleans up my environment before calling emerge, and which even explicitly passes through some variables which you might want to set temporarily in the environment.
I am sorry, we get now again a very wide output since I have implemented the thing with a huge "case":
Code:
#!/bin/sh
PATH='/usr/sbin:/usr/bin:/sbin:/bin'
printf '%s\n' "USER=${USER}"
# cd two times to erase OLDPWD
cd
cd /
IFS='
'
unset k
unset t
unset u
for i in `env|sort`
do   j=${i%%=*}
   case ${j} in
   *[!a-z0-9A-Z_]*|[0-9]*|'_'|PATH|PWD|OLDPWD|HOME|USER)
      :;;
   SHLVL|LANG*|LC*|DISPLAY|CCACHE*|'BASH_PROFILE'|CONFIG*|'GCC_SPECS'|KBUILD*|KERNEL*|'XZ_OPT'|RSYNC*|SSH*|TERM|'LD_'*|MANPATH|INFOPATH|KDE*|JAVA*|JDK*|ANT*|'COLON_SEPARATED'|'QT_'*|'XDG_'*|HG|GDK*|PRELINK*|GUILE*)
      k="${k} ${j}";;
   PYTHON_*|*SYNC*|*KNOW*|*GPO*|*PATCH*|*CCACHE*|USE_NONGNU|CC|CXX|LD|LINGUAS|MAKEOPTS|*KEYWORDS*|FLAG*|OPT*|NO*FLAG*|FEATURES|USE|*OFFLINE*|EMERGE*|PORT*|DISTDIR|PKGDIR|*COMMAND|*DELAY|GENTOO*|NOINST*|INST*|NODELTA|KEEP|GRSEC*|AUFS*|VIDEO*|BASHRC*|DELTA*|*CRAZY*|NOLOCALEPURGE|NOLAFILEREMOVE)
      t="${t} ${j}";;
   *)
      unset "${j}"
      u="${u} ${j}";;
   esac
done
Info() {
   [ -n "${2:++}" ] && printf '%s%s\n\n' "${1}" "${2}"
}
Info 'unset' "${u}"
Info 'keep' "${k}"
Info 'keep (temporary)' "${t}"
[ "${1}" = '-' ] && exit
exec /usr/bin/emerge "${@}"
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo Forums Feedback All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum