Hi Riku, Something I missed seeing in your original gfortran transition email, that maybe was left out because it was so obvious...
On 7/21/07, Riku Voipio <[EMAIL PROTECTED]> wrote: > For example, lapack3 is now: > > Package: lapack3 > Binary: lapack3, lapack3-test, lapack3-dev, lapack3-pic, lapack3-doc > Build-Depends: debhelper (>= 4), g77, refblas3-dev > > should become: > > Package: lapack3 > Binary: lapack3gf, lapack3-test, lapack3-dev, lapack3-pic, lapack3-doc > Build-Depends: debhelper (>= 4), gfortran, refblas3-dev (>= <first version > built with gfortran) I assume that the soname and filename of the library itself shouldn't change, just as in the g++ transition, right? So lapack3gf would continue to contain /usr/lib/liblapack.so.3, and therefore the new lapack3gf binary package (for instance) needs to Conflict and Replace the old lapack3 to prevent dpkg overwritten file complaints. Or is the plan to do this differently, renaming the library files and sonames to preserve parallel installability? I can imagine a lot of scientists will be unhappy that they need to recompile all their old locally built FORTRAN programs with a new compiler for them to keep working ... best regards, -- Kevin B. McCarty <[EMAIL PROTECTED]> Physics Department WWW: http://www.princeton.edu/~kmccarty/ Princeton University GPG: public key ID 4F83C751 Princeton, NJ 08544 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
