From owner-freebsd-arch@FreeBSD.ORG Sun Apr 11 14:20:19 2010 Return-Path: Delivered-To: arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59711106564A; Sun, 11 Apr 2010 14:20:19 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 084B98FC14; Sun, 11 Apr 2010 14:20:18 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o3BEHVRN091386; Sun, 11 Apr 2010 08:17:31 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 11 Apr 2010 08:17:39 -0600 (MDT) Message-Id: <20100411.081739.974702306123419358.imp@bsdimp.com> To: kientzle@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <4BC1188F.3060001@freebsd.org> References: <4BC1188F.3060001@freebsd.org> X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: yanefbsd@gmail.com, portmgr@FreeBSD.org, arch@FreeBSD.org Subject: Re: [RFC] Remove @owner and @user from package list X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Apr 2010 14:20:19 -0000 In message: <4BC1188F.3060001@freebsd.org> Tim Kientzle writes: : Garrett Cooper wrote: : > On Sat, Apr 10, 2010 at 3:57 PM, Garrett Cooper : > wrote: : >>> When doing some research, it appears that while functionality in : >>> theory exists for @owner and @user in the package list, it isn't : >>> actually used in the pkg_install code at all, adding unnecessary bloat : >>> to package lists; : > Doing some more digging, there are a handful of ports that I don't : > have installed that implement this functionality: : > @mode ... : > @owner ... : > @group ... : : I would certainly shed no tears if these went away. : : OTOH, I can see a use for them in pkg_create, to : set the mode/owner/group in the resulting tarball. : This would be good when building a package from a : port while running as non-root user. : : Of course, we could also do this from the mtree : description at either package creation time (reading : the mtree description and using it to set file properties : in the tarball) or package install time (using the : mtree description to set the final file properties : on disk). On the creation side, something like the above would be useful. makefs supports storing a tree's metadata in an .mtree file. We could obviate the need for those keywords if tar could be made to do the same thing :) I'm working on an unpriv'd installworld (where the meta data would go to the .mtree file, and the files would go into a tree owned as the user building). Mostly it is a port from NetBSD, but having tar that would respect this stuff would be great. Bonus points if the tag in mtree could be used as a file selector (either additively or subtractively). Warner