From owner-freebsd-ports@FreeBSD.ORG Tue Sep 27 18:47:58 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 68B29106566B; Tue, 27 Sep 2011 18:47:58 +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 407AD8FC0C; Tue, 27 Sep 2011 18:47:58 +0000 (UTC) Received: from g159.suse.de (charybdis-ext.suse.de [195.135.221.2]) by ainaz.pair.com (Postfix) with ESMTPSA id BB6243F416; Tue, 27 Sep 2011 14:47:56 -0400 (EDT) Date: Tue, 27 Sep 2011 20:47:52 +0200 (CEST) From: Gerald Pfeifer To: Lev Serebryakov In-Reply-To: <1859284079.20110913111221@serebryakov.spb.ru> Message-ID: References: <503309410.20110912205856@serebryakov.spb.ru> <865325899.20110912230621@serebryakov.spb.ru> <4E6E60C7.90304@FreeBSD.org> <181642832.20110912235833@serebryakov.spb.ru> <4E6E6607.2030104@FreeBSD.org> <801150301.20110913110114@serebryakov.spb.ru> <1859284079.20110913111221@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: ports@FreeBSD.org, Doug Barton Subject: Re: USE_GCC and unnesessary RUN_DENEDS on gcc port (Was: Print +REQUIRED_BY as tree?) 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: Tue, 27 Sep 2011 18:47:58 -0000 On Tue, 13 Sep 2011, Lev Serebryakov wrote: > Or, maybe automate this, as now port system warns user about "possible > network servers" -- check all installed binaries and libraries for > linkage with non-system-gcc libraries and add "run" dependency. But > I'm not sure it is easy to do, as it should be done after installation, > when, I afraid, adding RUN_DEPEND at this stage doesn't help, so this > automatic should make all depends-related work (+REQUIRED_BY / +CONTENT) > "by hands". I think you have a good observation here. One way of addressing it, which would be simpler and less effort and risk, is to split the large lang/gcc ports into smaller bits, including a run-time port, once the work on this infrastructure (that Linux distributions have been using for more than ten years) is in place. In other words, have something like a gcc-runtime package that falls out of the lang/gcc port and covers all those needs. (That's not the minimum, assuming we still have something -- bet it GCC 4.2 or LLVM based in the base system -- but quite small.) Gerald