JF,
My mistake. I meant that a new entry for gcc43 had to be
added to the gcc42 package when gcc43 was added to fink.
One could rebuild gcc43 with the older gcc42-4.2.2-1001
package installed but not install it without manually
removing gcc42. There is no way around this. Each time
a new gcc4X package is added we have to update the
Conflicts/Replaces fields to contain the new package.
Jack
ps I could add bogus entries for gcc44, gcc45, etc in
the packaging well in advance of any possible release
but I thought adding references to non-existent packages
was bad form.
On Wed, Mar 12, 2008 at 06:48:39PM +0100, Jean-Francois Mertens wrote:
> Jack Howarth wrote:
>> Each time a new gcc4X package is created
>> it will be necessary for users to update to the previous ones
>> to revisions which have BuildConflicts on the newer ones.
>
> Adding a buildconflict should not require a rev-up.
>
> JF Mertens
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-users
