On Thu, 2011-02-24 at 22:15 +0100, Matthias Klose wrote: > On 24.02.2011 21:15, Adam D. Barratt wrote: > > [...] > >> Matthias also responded requesting: > >> > >> I see that both the runtime library and the -dev packages have > >> different package names. But to be able to still use gmp3 for > >> existing GCC versions, please change the source name too, such > >> that gmp3 is still available in unstable after the upload of gmp5. > >> > >> Shall I go ahead and upload the source gmp5? Then both gmp versions > >> will co-exist in the repository and packages can choose to move to > >> gmp5 at their leisure. > > > > After some further investigation, it looks like this isn't feasible. > > Neither gmp 4.3.2 nor 5.0.1 version their symbols and with both versions > > in the archive simultaneously and co-installable, there's a reasonable > > risk of a process ending up with both libraries loaded in to its address > > space, which is generally not a good idea. > > did you check, that all gcc versions do build with the new version on all > architectures, and that the gcc testsuite doesn't show regressions with the > new > version? will gcc continue to work, while re-building mpfr and mpclib with > the > new gmp?
Steve's mail to this thread less than a week ago said he hadn't done any test rebuilds at all; I suspect the chances that he's gone on to build and test multiple GCC versions on multiple architectures in the meantime are small. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1298582383.22974.489.ca...@hathi.jungle.funky-badger.org
