From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20609 invoked by alias); 13 Dec 2007 21:38:32 -0000 Received: (qmail 20602 invoked by uid 22791); 13 Dec 2007 21:38:31 -0000 X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,BAYES_00,DK_POLICY_SIGNSOME,UNPARSEABLE_RELAY X-Spam-Check-By: sourceware.org Received: from rgminet01.oracle.com (HELO rgminet01.oracle.com) (148.87.113.118) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 13 Dec 2007 21:38:18 +0000 Received: from agmgw1.us.oracle.com (agmgw1.us.oracle.com [152.68.180.212]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id lBDLbaeo001475; Thu, 13 Dec 2007 14:37:36 -0700 Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by agmgw1.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id lBD4vZFA004854; Thu, 13 Dec 2007 14:37:36 -0700 Received: from alchar.org by acsmt359.oracle.com with ESMTP id 6350625411197581829; Thu, 13 Dec 2007 15:37:09 -0600 Date: Thu, 13 Dec 2007 21:38:00 -0000 From: Kris Van Hees To: frysk Cc: Andrew Cagney Subject: Re: enabling shared builds Message-ID: <20071213213703.GA2300@oracle.com> References: <476146B5.7020606@redhat.com> <47614961.5090901@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47614961.5090901@redhat.com> User-Agent: Mutt/1.5.16 (2007-06-09) X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2007-q4/txt/msg00222.txt.bz2 > Andrew Cagney wrote: > - switch to install-tree testing > Would mean breaking configure convention and set --prefix=. On the other > hand it would mean only testing one way. Definitely a big 'no' on this one. For one, forcing an install of development builds in order to be able to test it is asking for trouble. Secondly, it is (hopefully) going to be more likely in the future that a system will have frysk already installed as part of the OS install, and a development build shouldn't wipe out the installed version for sure. Thirdly, it is common practice with software projects to follow a 'build -> test -> install' sequence, which is generally the most sensible way because you wouldn't want to install something that is broken, i.e. test before you install. Cheers, Kris