From mint-bounce@lists.fishpool.fi Tue Jan 29 18:16:57 2008 To: mint From: Peter Slegg Subject: Re: [MiNT] GCC 4.2.2 RPM build.... Reply-To: Peter Slegg X-Mailer: MyMAIL Rev:1.89.13600 (Atari/(STiK/STinG/GlueSTiK)) X-Hardware: Atari Milan MIME-Version: 1.0 Date: Tue, 29 Jan 2008 23:12:16 +0200 (GMT) Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 X-MSMail-Priority: Normal Message-Id: <003011e7.019a88ca4650@smtp.freeola.net> References: <479CEF8A.60806@freesbee.fr> In-Reply-To: 479CEF8A.60806@freesbee.fr X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: p.slegg@scubadivers.co.uk Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id m0TNGvAW021792 Hats off and (virtual) drinks all round to all those involved in this work to update GCC and ultimately a lot of other things. A couple of questions and ideas: Is there anything we can do that will minimise the amount of work needed when the next release of GCC emerges ? If a lot of RPMs are to be updated with GCC 4 should they be on a separate Sparemint page or is this not necessary ? What I mean is, if a package is updated will it be ok to install with older stuff. Regards, Peter