From owner-freebsd-stable@FreeBSD.ORG Thu Aug 28 19:32:28 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 30F5A16A4C0 for ; Thu, 28 Aug 2003 19:32:28 -0700 (PDT) Received: from lariat.org (lariat.org [63.229.157.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E81A043F93 for ; Thu, 28 Aug 2003 19:32:26 -0700 (PDT) (envelope-from brett@lariat.org) Received: from mustang.lariat.org (IDENT:ppp1000.lariat.org@lariat.org [63.229.157.2]) by lariat.org (8.9.3/8.9.3) with ESMTP id UAA03742; Thu, 28 Aug 2003 20:32:17 -0600 (MDT) X-message-flag: Warning! Use of Microsoft Outlook renders your system susceptible to Internet worms. Message-Id: <4.3.2.7.2.20030828202159.0306e7f0@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 28 Aug 2003 20:32:07 -0600 To: Colin Percival , stable@freebsd.org From: Brett Glass In-Reply-To: <5.0.2.1.1.20030828130814.01c6dfd8@popserver.sfu.ca> References: <4.3.2.7.2.20030828133145.0313d860@localhost> <5.0.2.1.1.20030828110441.02d9f580@popserver.sfu.ca> <4.3.2.7.2.20030828120019.0324b6a0@localhost> <5.0.2.1.1.20030828103403.02d683a8@popserver.sfu.ca> <200308280638.AAA19221@lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: Re: Need to build some systems this week. Snapshots? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Aug 2003 02:32:28 -0000 At 02:22 PM 8/28/2003, Colin Percival wrote: > FreeBSD Update only concerns itself with the base FreeBSD distribution -- I simply don't have the resources to build any more than that. However, one simple approach to the ports problem would be to > # find /usr/local/ -perm +111 -type f -exec file {} \; | grep "statically linked" | cut -f 1 -d ':' >and rebuild the applicable ports. Now that I think about it, I might add some sort of functionality like that (providing a listing of ports which need to be rebuilt) into a future version of FreeBSD Update. This would be a big help. It would be even better if it could also identify binary packages that need updating (since this, after all, has historically been one of the biggest problems with updating FreeBSD. Of course, the problem with packages is more serious than with ports, because the project has always (for no reason that I can see other than habit) treated binary packages as "second class citizens" compared to ports. Ports can be updated at any time and recompiled. But if there's a bug in a program which has been installed as a package, there's no way for a user to get a freshened package until the next release of the OS! While the project builds binary snapshots of the OS itself nightly, it doesn't rebuild and post packages in between releases. Yes, a user can sometimes uninstall the package and reinstall the same application as a port (after fixing the relevant libraries). But if disk space is tight, or the system is embedded or doesn't include a compiler (embedded or semi-embedded implementations of the BSDs are becoming more and more common), this might not be possible. I'd like to see the project rebuild binary packages regularly so that a user (or a utility such as your updater) can fetch repaired versions of them as needed. It should be easy to tell which ones need rebuilding, so that it's unnecessary to rebuild the entire collection every night. --Brett