From owner-freebsd-stable@FreeBSD.ORG Sun Jun 3 23:30:24 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 851CD1065768 for ; Sun, 3 Jun 2012 23:30:24 +0000 (UTC) (envelope-from marka@isc.org) Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by mx1.freebsd.org (Postfix) with ESMTP id 0EE4A8FC1B for ; Sun, 3 Jun 2012 23:30:24 +0000 (UTC) Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 326375F9985; Sun, 3 Jun 2012 23:30:04 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:11c3:b721:6977:1aa6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 767AA216C33; Sun, 3 Jun 2012 23:30:02 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id B3C84213527E; Mon, 4 Jun 2012 09:30:04 +1000 (EST) To: Erich From: Mark Andrews References: <4069760.8WmX7zQx9F@x220.ovitrap.com> <2156532.vx6SHRoqL8@x220.ovitrap.com> In-reply-to: Your message of "Sun, 03 Jun 2012 19:43:03 +0700." <2156532.vx6SHRoqL8@x220.ovitrap.com> Date: Mon, 04 Jun 2012 09:30:04 +1000 Message-Id: <20120603233004.B3C84213527E@drugs.dv.isc.org> X-Spam-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00, T_RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mx.ams1.isc.org Cc: freebsd-stable@freebsd.org, Chris Rees , Chris Nehren Subject: Re: Why Are You NOT Using FreeBSD? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2012 23:30:24 -0000 In message <2156532.vx6SHRoqL8@x220.ovitrap.com>, Erich writes: > Hi, > > On 03 June 2012 AM 9:15:14 Chris Rees wrote: > > On Jun 3, 2012 5:26 AM, "Erich" wrote: > > > > > > Hi, > > > > > > On 02 June 2012 PM 2:56:01 Chris Nehren wrote: > > > > On Sat, Jun 02, 2012 at 14:11:06 -0400 , Paul Mather wrote: > > > > > I'm not sure what the solution is for the end user. I know I get > > > > > somewhat leery of updating my ports if I see a large number of change > s > > > > > coming via portsnap (like the 4000+ that accompanied the recent libpn > g > > > > > upgrade) and there is nothing new in UPDATING (which, happily wasn't > > > > > the case with the libpng upgrade). Usually, I wait a while for the > > > > > dust to clear and an UPDATING entry potentially to appear. > > > > > > > > If you're concerned about things breaking, don't follow the bleeding > > > > edge. This seems to be common sense. > > > > > > is there a second version of the ports tree available? > > > > > > What is the response of the list if you want to install a new package > > with you old ports tree? > > > > > > > The response is "Don't ask for support if you do that", I'm afraid. > > > > No major OS I can think of allows you to mix and match like that (though I > > could be wrong). > > it is new to me that Microsoft asks for a Windows update when a new Office ve > rsion appears at the scene. No. It just silently does the OS update by installing new sets of libraries if required. When we install our software on a Windows machine we update the OS by installing the lastest C runtime libraries. We use Microsoft's installer but we do it. We also ship a private copy of the OpenSSL and libxml libraries we use. > Microsoft also does not ask to update all other applications before the lates > t Office can be installed. And you don't have to do that for FreeBSD if you don't want to. For each application you have you can put all the dependancies in its own tree. Apple does this for MacOS. The ports system defaults are to use a common build/runtime tree but at the cost of a little more disk space each major application could have its own build/runtime tree. This is a tradeoff. Most of the time having a shared set of libraries is a win, but just occasionally, it is a big pain. I've got a system where the X server is running a completely different set of libraries compared to the X applications. I just couldn't get the new server to work. I just took all the old server package and all its dependencies and installed it in a new location. This has a bit more that what is actually requires as I don't need all the header files but it works. For tools that are critical I would suggest building a seperate build / runtime tree. Disk space is relatively cheap. One thing that could help is splitting library packages into runtime / buildtime sub packages. That way you can reduce the foot print for a runtime install. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org