From mint-bounce@lists.fishpool.fi  Wed Jan 30 06:08:28 2008
Message-ID: <20080130105944.emaa9fw0cos00os0@pop.freeola.net>
Date: Wed, 30 Jan 2008 10:59:44 +0000
From: p.slegg@scubadivers.co.uk
To: mint@lists.fishpool.fi
Subject: Re: [MiNT] GCC 4.2.2 RPM build....
References: <479CEF8A.60806@freesbee.fr>
	<003011e7.019a88ca4650@smtp.freeola.net> <479FC448.8040507@freesbee.fr>
In-Reply-To: <479FC448.8040507@freesbee.fr>
MIME-Version: 1.0
Content-Type: text/plain;
	charset=;
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.0.3)
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: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>

Quoting Vincent Rivi`ere <vincent.riviere@freesbee.fr>:

> Peter Slegg wrote:
>> Is there anything we can do that will minimise the amount of work
>> needed when the next release of GCC emerges ?
>
> The master word is: automation
> For every package, we should have a source package and a rock-solid 
> build script for building the binary package

I don't know of this is relevant but I wondered if there were any
changes that should be fed-back to the GCC/GNU maintainers that
might help FreeMint in the future ?

Peter