From owner-freebsd-ports@FreeBSD.ORG Sun Oct 7 17:22:52 2007 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 246F116A418 for ; Sun, 7 Oct 2007 17:22:52 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from cp65.agava.net (cp65.agava.net [89.108.66.215]) by mx1.freebsd.org (Postfix) with ESMTP id CAEF613C480 for ; Sun, 7 Oct 2007 17:22:50 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from [213.148.20.85] (helo=nexii.panopticon) by cp65.agava.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.44 (FreeBSD)) id 1IeZq4-000DnO-Mf; Sun, 07 Oct 2007 21:22:48 +0400 Received: from hades.panopticon (hades.panopticon [192.168.0.2]) by nexii.panopticon (Postfix) with ESMTP id 0C5361703D; Sun, 7 Oct 2007 21:24:01 +0400 (MSD) Received: by hades.panopticon (Postfix, from userid 1000) id BF8354048; Sun, 7 Oct 2007 21:24:17 +0400 (MSD) Date: Sun, 7 Oct 2007 21:24:17 +0400 From: Dmitry Marakasov To: Jeremy Messenger Message-ID: <20071007172417.GA1082@hades.panopticon> Mail-Followup-To: Jeremy Messenger , freebsd-ports@freebsd.org References: <20071004190304.GA9491@hades.panopticon> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cp65.agava.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [26 6] X-AntiAbuse: Sender Address Domain - amdmi3.ru X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-ports@freebsd.org Subject: Re: Idea: static builds 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: Sun, 07 Oct 2007 17:22:52 -0000 * Jeremy Messenger (mezz7@cox.net) wrote: > How do you deal with the security? It will be required for all ports that > depend on a port to be rebuild, so bump the PORTREVISION will be need. But > what about for non-static that don't need to be bump? A solution for that > might be need too. > > I have no object with static build as long as it is flexible and optional > (disable/enable). I know all the negative sides of static builds, as much larger binary sizes, memory consumption, upgrade problems when dependent library is vulnerable/updated etc, but I just thought that it could be useful sometimes. For example, I'd rather install static package of some Gnome/KDE app (while I don't use Gnome/KDE) than install all dependencies (that are mandatory just because somebody didn't bother to OPTIONSify, say, kdelibs). What I propose is just an option that may be usedul, but don't guarantee anything. Like, for example, WITH_DEBUG. But, yes, it would be nice to indicate that the port should be rebuild if any of libs it use are updated, I need to think about it. -- Best regards, Dmitry Marakasov mailto:amdmi3@amdmi3.ru