Alan McKinnon <[EMAIL PROTECTED]> writes:
[...] >> Can anyone interpret this emerge failure and have some educated >> guesses what I should do to get it to compile. That message follows >> the eix output below. > > http://forums.gentoo.org/viewtopic-p-4210019.html?sid=a282fd302189d999924b214267ec5b90 > > especially last 4 posts > > Apparently it's a bug, and has been fixed in later versions. You are > using a stable 2004 version, in your position I would unmask ksh and > emerge the latest unstable I see... thanks. That does sound like a way around it., I may just start using bash instead for the future... Having this happen has made me rethink my ( non-thought out) choice of shells. I see where it can cause some grief at a time when you don't want to be horsing around with that kind of problem. I'm not a very sophisticated shell script programmer. One thing I liked about ksh93 was its ability to match on regex. Something bash couldn't do not so long ago. I haven't been paying attention to bash development but having this problem, I did start investigating and finding that modern bash can do most if not all of what I liked about ksh93. It can match like this if [[ $1 =~ ^[0-9]+$ ]];then [...] fi Forcing a match of number only by regex. Instead of trying to do it with a pattern match. And a sort of double reverse loop de loop negation I sometimes find useful. (since there is no `!~' operator like perl or awk) if [[ ! ( $1 =~ ^[0-9]+$ )]];then [...] fi I'm beginning to think I may just drop ksh93. Unfortunately, I've grown quite accustomed to using `print' instead of `echo -e' so I will have to replace that in a couple dozen scripts... otherwise the scripts seem to run fine under bash. (so far.. I haven't tested all of them yet) -- gentoo-user@lists.gentoo.org mailing list
