Dave Vasilevsky wrote: []
I wouldn't object to synchronizing the version numbers of the GCC 3.1 virtual package and the real package. Currently the virtual one is at version '3.1' and the real one uses the build number '1175', it should be possible to have them both use '1:3.1-1175' for example. Perhaps there is a pressing reason why they need to be different?
What should urgently be done is to give the virtual gcc3.1 package a version equal or higher than the Fink package's. The reason is that right now, if you install the legacy package, your next "fink update-all" will install Fink's gcc3.1 if you didn't have it installed yet. This is highly absurd and will certainly provoke some justified anger among unsuspecting users.
Since the version number of the virtual package cannot be changed immediately without releasing a new fink version, something should be done about the Fink gcc3.1 package, like change its version to 0.1175-6, changing its name, or scrapping it altogether.
-- Martin ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
