| 1 |
On 6/22/11 4:47 PM, Andreas K. Huettel wrote: |
| 2 |
> Am Mittwoch 22 Juni 2011, 16:35:07 schrieb Matthew Summers: |
| 3 |
>> |
| 4 |
>> Hey Justin, |
| 5 |
>> |
| 6 |
>> One thing to note is that a few various python modules, like numpy, |
| 7 |
>> really benefit from fortran. While many people using numpy are |
| 8 |
>> scientists, many are not and further there are various modules that |
| 9 |
>> depend on numpy that non-science folks use. I, for one, care little |
| 10 |
>> about where that flag is set, since I have manually set that USE for |
| 11 |
>> years now in make.conf. I am simply hoping to make you aware of the |
| 12 |
>> fact that there are potential cases that could be easily overlooked. |
| 13 |
>> |
| 14 |
>> Thanks! |
| 15 |
>> Matt |
| 16 |
>> |
| 17 |
> |
| 18 |
> ... and there are also typical end user software packages like digikam and kipi-plugins for photo processing, which rely e.g on opencv for face recognition, red eye removal, ... |
| 19 |
> |
| 20 |
|
| 21 |
So then, |
| 22 |
|
| 23 |
lets make a clear decision how we should handle the fortran USE. |
| 24 |
|
| 25 |
1. leave it as it is as global USE enabled. |
| 26 |
|
| 27 |
2. enable it as default for gcc |
| 28 |
|
| 29 |
3. let package maintainers fix their packages, |
| 30 |
means depend on fortran by default where it is the best and/or needed |
| 31 |
|
| 32 |
thanks justin |
Archives