From owner-svn-ports-head@freebsd.org Tue Aug 28 11:51:55 2018 Return-Path: Delivered-To: svn-ports-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A941E108918B; Tue, 28 Aug 2018 11:51:55 +0000 (UTC) (envelope-from osa@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5FBC7800DD; Tue, 28 Aug 2018 11:51:55 +0000 (UTC) (envelope-from osa@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 975) id 58975CA6; Tue, 28 Aug 2018 11:51:55 +0000 (UTC) Date: Tue, 28 Aug 2018 11:51:55 +0000 From: "Sergey A. Osokin" To: Yuri Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r478259 - in head/science: ghemical libghemical libint mpqc Message-ID: <20180828115155.GF30926@FreeBSD.org> References: <201808272256.w7RMuioD090614@repo.freebsd.org> <20180828012033.GE30926@FreeBSD.org> <3724ce3d-8eba-b1df-cb0c-fd3f5ed35d77@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <3724ce3d-8eba-b1df-cb0c-fd3f5ed35d77@freebsd.org> User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Aug 2018 11:51:55 -0000 On Mon, Aug 27, 2018 at 07:15:48PM -0700, Yuri wrote: > On 8/27/18 6:20 PM, Sergey A. Osokin wrote: > > thanks for your hard work and take over maintainership. > > You are welcome! > > > I'd prefer to see the static library for the application as > > well as shared libraries cause it help in many cases. > > > > Please let me know if you have any questions. > > Static libraries are mostly useful within the build, when they are > produced and consumed internally. Otherwise, shared libraries are > generally better. > > Static library cons: > 1. They cause other binaries to become larger. > 2. They consume space on disk when installed along with the shared > libraries. > 3. They obscure which external libraries are used by the project. > 4. They make fixing security vulnerabilities more difficult. > > > Static library pros: > 1. They allow for a marginally better performance. > 2. They are a must when the target binary needs to be static for > security or other reasons (for example tor). There are very few cases > when static executables are needed. Thanks for the pros and cons, Yuri. Is there a chance to revert back changes related to the static library to return it back? -- Sergey Osokin