From owner-cvs-src@FreeBSD.ORG Tue Sep 14 15:43:36 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB4E616A4CE; Tue, 14 Sep 2004 15:43:36 +0000 (GMT) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51C0843D3F; Tue, 14 Sep 2004 15:43:36 +0000 (GMT) (envelope-from kientzle@freebsd.org) Received: from freebsd.org (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id i8EFhV90035992; Tue, 14 Sep 2004 08:43:31 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <414711A3.1040608@freebsd.org> Date: Tue, 14 Sep 2004 08:43:31 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031006 X-Accept-Language: en-us, en MIME-Version: 1.0 To: obrien@freebsd.org References: <200403192237.i2JMb7O3096581@repoman.freebsd.org> <20040914071843.GA66472@dragon.nuxi.com> In-Reply-To: <20040914071843.GA66472@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: cvs-src@freebsd.org cc: src-committers@freebsd.org cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/lib/libarchive Makefile archive.harchive_entry.3 archive_read.carchive_read_support_format_cpio.c archive_read_support_format_gnutar.c ... X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2004 15:43:36 -0000 David O'Brien wrote: > On Fri, Mar 19, 2004 at 02:37:07PM -0800, Tim Kientzle wrote: > >>kientzle 2004/03/19 14:37:06 PST >> >> FreeBSD src repository >> >> Modified files: >> lib/libarchive Makefile archive.h archive_entry.3 > > .. > >> Log: >> Many fixes: >> * Disabled shared-library building, as some API breakage is >> still likely. > > > Hi Tim, > > Is it safe to turn shared libs back on? I think the API is pretty solid now, so it should be safe. Go for it! Tim