Re: Our GCC-4.8 is broken

On 12/18/2013 09:52 AM, Keith Marshall wrote:
> In the short term, I'm inclined to suggest rolling back to GCC-4.7, as
> our default offering, and ripping all of the broken packages out of the
> on-line catalogue.
> 

I agree, this would give us time to solve the bugs and to redo the
packaging carefully.

How would this downgrade be implemented? Other package managers have the
concept of an epoch, that allows downgrades (in the absence of an
explicit epoch, zero is implied):

4.8.1-4 (epoch = 0) < 1:4.7.2-1 (epoch = 1)

Does mingw-get already supports epochs?

Another useful construct is "conflicts", which allows for packaging
renaming (installing one forces removal of the other, like with versions
upgrades, but allowing for differing base names).

Regards,

Cesar


------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk