Date: Thu, 28 Apr 2005 20:02:05 +1000 From: Sam Lawrance <boris@brooknet.com.au> To: Edwin Groothuis <edwin@mavetju.org> Cc: ports@freebsd.org Subject: Re: Why can't pkg-plist list directories? Message-ID: <1114682525.17690.28.camel@dirk.no.domain> In-Reply-To: <20050428080341.GM1175@k7.mavetju> References: <1114610923.45212.16.camel@dirk.no.domain> <20050428080341.GM1175@k7.mavetju>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1114682525.17690.28.camel>