From owner-freebsd-ports@FreeBSD.ORG Mon Jun 11 22:45:31 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 502D71065670; Mon, 11 Jun 2012 22:45:31 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from ainaz.pair.com (ainaz.pair.com [209.68.2.66]) by mx1.freebsd.org (Postfix) with ESMTP id 28D068FC08; Mon, 11 Jun 2012 22:45:31 +0000 (UTC) Received: from ip-109-84-112-234.web.vodafone.de (ip-109-84-112-234.web.vodafone.de [109.84.112.234]) by ainaz.pair.com (Postfix) with ESMTPSA id 456D83F421; Mon, 11 Jun 2012 18:45:28 -0400 (EDT) Date: Tue, 12 Jun 2012 00:45:22 +0200 (CEST) From: Gerald Pfeifer To: Doug Barton , Baptiste Daroussin In-Reply-To: <20120610175859.GN60433@ithaqua.etoilebsd.net> Message-ID: References: <4FD4140F.4010209@FreeBSD.org> <20120610175859.GN60433@ithaqua.etoilebsd.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Chris Rees , Heino Tiedemann , rotkap@gmx.de, freebsd-ports@freebsd.org Subject: Re: firefox 13.0,1 needs lang/gcc46 -- to RUN?! X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 22:45:31 -0000 On Sat, 9 Jun 2012, Doug Barton wrote: > In an ideal world, we would have separate packages for the runtime libs > and the build tools so that packages could be more portable, but I would > imagine that would be a lot of work. I looked into that last year and found that the FreeBSD ports infrastructure was not exactly helpful. Ideally I would want something like gcc46-runtime and gcc46-java and gcc46 itself, where -runtime is a hard dependency for gcc46 and -java optional. Short of building lang/gcc46 a couple of times via slave ports and packaging different aspects by virtue of different slave ports, or having gcc46 also include the contents of gcc46-runtime, the introduction of a gcc46-DONT-USE-JUST-USED-FOR-SUBPACKAGES dummy port was the only idea I came up with. None of the three approaches really convinced me. On Sun, 10 Jun 2012, Baptiste Daroussin wrote: > Yes that would be a lot of but it is the way we are doing. the upcoming > stagedir will open the door to easy package splitting and then allow > easily to split gcc into something like gcc-libs and gcc package or > something like that. Lovely. Looking forward to that! (Chris also indicated he had an idea, let's see. Whatever works. ;-) Gerald