Which makes me wonder why when I downloaded the beta of 7.2 for testing,
I was given a Cooker directory for doing updates from. Perhaps a beta
directory should have been made off of cooker when it was decided that
the cooker of then would become the 7.2 beta.
Now it seems that instead of testing what I thought were updates to
beta, I'm testing cooker packages. The instructions on the page
regarding the downloading of 7.2b3 for testing should change the
directions on where to get the updates from so those of who want to help
get 7.2 tested and fixed for production can, and those who want to keep
cooker rolling along toward Mdk7.x and/or GCC3.00 can do so.
Chmouel Boudjnah wrote:
>
> Bryan Paxton <[EMAIL PROTECTED]> writes:
>
> > Why is mandrake going to a cvs snapshot of gcc ?
> > You would think of all the much about redhat doing so, you'd think more than
> > twice about a move like this.
> > And even statement(I'd more likely call it an advisory) from the gcc team ?
>
> If you notice we have the flag and not [CHRPM] and not [FROZEN-CHRPM]
> that mean it for cooker not for frozen install.
>
> --
> MandrakeSoft Inc http://www.chmouel.org
> Paris, France --Chmouel
--
Digital Wokan
Tribal mage of the electronics age
Guerilla Linux Warrior
