From owner-freebsd-ports@FreeBSD.ORG  Thu Apr 28 10:01:46 2005
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 34CBC16A4CE
	for <ports@freebsd.org>; Thu, 28 Apr 2005 10:01:46 +0000 (GMT)
Received: from bloodwood.hunterlink.net.au (smtp-local.hunterlink.net.au
	[203.12.144.17])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E62C543D31
	for <ports@freebsd.org>; Thu, 28 Apr 2005 10:01:44 +0000 (GMT)
	(envelope-from boris@brooknet.com.au)
Received: from ppp27B8.dyn.pacific.net.au (ppp27B8.dyn.pacific.net.au
	[61.8.39.184])j3SA1Whw023003;	Thu, 28 Apr 2005 20:01:42 +1000
From: Sam Lawrance <boris@brooknet.com.au>
To: Edwin Groothuis <edwin@mavetju.org>
In-Reply-To: <20050428080341.GM1175@k7.mavetju>
References: <1114610923.45212.16.camel@dirk.no.domain>
	 <20050428080341.GM1175@k7.mavetju>
Content-Type: text/plain
Date: Thu, 28 Apr 2005 20:02:05 +1000
Message-Id: <1114682525.17690.28.camel@dirk.no.domain>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.2 FreeBSD GNOME Team Port 
Content-Transfer-Encoding: 7bit
cc: ports@freebsd.org
Subject: Re: Why can't pkg-plist list directories?
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Apr 2005 10:01:46 -0000

On Thu, 2005-04-28 at 18:03 +1000, Edwin Groothuis wrote:
> On Thu, Apr 28, 2005 at 12:08:41AM +1000, Sam Lawrance wrote:
> > Aside from the fact that the pkg_* tools don't currently support it, is
> > there a reason why we use @dirrm in packing lists rather than just
> > listing the directories?
> 
> Foolproofing.
> 
> If I copy a file to etc/foo where foo is a directory, but I forgot
> to create the directory first I end up with the file foo in etc/.
> Having the pkg-plist explicitely stating it as a directory, it will
> throw an error and the maintainer (and eeeeeeverybody else) will
> know he made a mistake.

But if the packing list contained, for example

	etc/foo/somefile

and either

	@dirrm etc/foo

or just 

	etc/foo

Then etc/foo/somefile would not be found and the error would be known in
either case.  Although, I do in part see your point... there's less
ambiguity with @dirrm.

In which case, perhaps pkg_create could be modified to add directories
listed with @dirrm to the tarball so empty dirs, permissions and modes
are preserved.