Re: Location for Fortran90 module files

2013-08-09 Thread Michael Banck
On Fri, Jul 26, 2013 at 02:37:15PM +0200, Matthias Klose wrote: Am 25.07.2013 14:25, schrieb Michael Banck: What to do about the compatibilty is a different matter, did this come up before? looks like one hand in the debian-science team doesn't know what the other hands are doing ...

Re: Location for Fortran90 module files

2013-07-26 Thread Matthias Klose
Am 25.07.2013 14:25, schrieb Michael Banck: What to do about the compatibilty is a different matter, did this come up before? looks like one hand in the debian-science team doesn't know what the other hands are doing ... See #714730, even on the debian-science ML. -- To UNSUBSCRIBE, email

Re: Location for Fortran90 module files

2013-07-26 Thread Andreas Tille
Hi Matthias, On Fri, Jul 26, 2013 at 02:37:15PM +0200, Matthias Klose wrote: Am 25.07.2013 14:25, schrieb Michael Banck: What to do about the compatibilty is a different matter, did this come up before? looks like one hand in the debian-science team doesn't know what the other hands

Re: Location for Fortran90 module files

2013-07-26 Thread Matthias Klose
Am 26.07.2013 15:35, schrieb Andreas Tille: BTW, it would have been perceived even without the unfriendly tenor. In case you might not know the team is maintaining a wide range of packages and so there is not always a need to know about specific Fortran issues. well, apparently you did

Re: Location for Fortran90 module files

2013-07-26 Thread Andreas Tille
Hi Matthias, On Fri, Jul 26, 2013 at 03:55:18PM +0200, Matthias Klose wrote: Am 26.07.2013 15:35, schrieb Andreas Tille: BTW, it would have been perceived even without the unfriendly tenor. In case you might not know the team is maintaining a wide range of packages and so there is not

Location for Fortran90 module files

2013-07-25 Thread Michael Banck
Hi, Fortran90 compiler produce module files (.mod) when compiling modules, those are supposed to included by Fortran90 applications like .h header files for C/C++. However, those module files are kinda precompiled and compiler- and even compiler-version dependent in the sense that there is no