Re: fw: gfortran transition release goal proposal
- To: Riku Voipio <firstname.lastname@example.org>
- Cc: email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org
- Subject: Re: fw: gfortran transition release goal proposal
- From: Carlo Segre <email@example.com>
- Date: Sat, 21 Jul 2007 23:22:44 -0500 (CDT)
- Message-id: <[🔎] Pine.LNX.firstname.lastname@example.org>
- Reply-to: email@example.com
- In-reply-to: <[🔎] 20070721221914.GA19890@kos.to>
- References: <[🔎] 20070721221914.GA19890@kos.to>
My fortran packages are non-free (pgplot5) or contrib (ifeffit). I have
not yet had any time to determine if these are going to cause problems. I
am sort of worried though because pgplot5 is quite particular.
On Sun, 22 Jul 2007, Riku Voipio wrote:
The proposal to transition from the outdated g77 to gfortran did
not result any comments. Which rises the suspicion that the maintainers
of affected packages are not reading debian-release or debian-toolchain.
If you have suggestions, critique, or you are busy but accept NMU'ing
your packages for gfortran transition.. please speak now.
Some of the packages gfortran transition affects are also affected by
the long double transition. This includes atleast the following fortran
lam, atlas3, fftw3, hdf5, mpich1.0, petsc, pdl
Therefor, I think it would make sense to start g77 -> gfortran
transition promptly, to avoid transitioning same packages twice.
Carlo U. Segre -- Professor of Physics
Associate Dean for Special Projects, Graduate College
Illinois Institute of Technology
Voice: 312.567.3498 Fax: 312.567.3494
firstname.lastname@example.org http://www.iit.edu/~segre email@example.com