From owner-freebsd-hackers@FreeBSD.ORG Wed May 26 20:20:24 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3E0416A4CE for ; Wed, 26 May 2004 20:20:24 -0700 (PDT) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DB9143D41 for ; Wed, 26 May 2004 20:20:24 -0700 (PDT) (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 i4R3Jk90092804; Wed, 26 May 2004 20:19:46 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <40B55E4C.7020504@freebsd.org> Date: Wed, 26 May 2004 20:19:40 -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: Brenden Grace References: <1085603749.2367.35.camel@linux.local> In-Reply-To: <1085603749.2367.35.camel@linux.local> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: pkg_create @cwd and @srcdir X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2004 03:20:24 -0000 Brenden Grace wrote: > In this thread: > http://lists.freebsd.org/pipermail/freebsd-hackers/2003-June/001673.html > > some people seem to think that @cwd is broken. The man pages do not > explicitly state how @cwd should operate, but currently the directory > must exist for pkg_create to run properly. > > This is extremely annoying because build machines *must* create the > final directory structure of the target install before the package can > be created. > > So my question is, does the 5.2.1 version of pkg_create contain a bug or > is pkg_create really just very limited? Try it with bsdtar as the system default tar and see if that behaves any differently. (WITH_BSDTAR=1 in /etc/make.conf). I had read the above thread shortly before I designed bsdtar's cwd handling, and it should work. bsdtar stores directory change requests but doesn't actually try to chdir() until it sees a file. That way, extraneous cwd requests get silently ignored, rather than causing it to abort. Let me know... Tim Kientzle