| 1 |
> Well it's easy using chained commands, but a single bash expansion will fail as some point as you seen and make the whole command fail. |
| 2 |
|
| 3 |
possible workaroud: pipe errors to /dev/null. |
| 4 |
|
| 5 |
> |
| 6 |
> Something like this maybe : |
| 7 |
> |
| 8 |
> if [ -f python2.? ] ; then |
| 9 |
> echo "python2.6 stuff" |
| 10 |
> elif [ -f python2.?.exe ] ; then |
| 11 |
> echo "in python2.6.exe stuff" |
| 12 |
> else |
| 13 |
> echo "error ?" |
| 14 |
> fi |
| 15 |
> |
| 16 |
|
| 17 |
Ooops. That will blow up the code. There are 5 or 6 occurrances of |
| 18 |
this in the file. How about putting the suffix itself into a variable? |
| 19 |
|
| 20 |
For now I took the easy way by simply appending the .exe suffix. At |
| 21 |
least the python package is merged now, but some modules are broken. |
| 22 |
|
| 23 |
So the final solution has to wait a little. I will try to emerge |
| 24 |
portage now. If it works the second milestone is reached. |
| 25 |
|
| 26 |
Al |
Archives