From owner-freebsd-current@FreeBSD.ORG Fri Sep 19 03:13:09 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AC0216A4B3; Fri, 19 Sep 2003 03:13:09 -0700 (PDT) Received: from rod.inty.net (rod.inty.net [195.224.93.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5199943FDD; Fri, 19 Sep 2003 03:13:07 -0700 (PDT) (envelope-from paul@freebsd-services.com) x-previous-hop: 212.50.178.178 Received: from inty.hq.inty.net (inty-untrusted-aztec-west.inty.net [212.50.178.178]) by rod.inty.net (8.12.9/8.12.9) with ESMTP id h8JACmiv041435; Fri, 19 Sep 2003 11:12:49 +0100 (BST) Received: from [10.0.1.111] ([10.0.1.111]) by inty.hq.inty.net (8.12.1/8.12.1) with ESMTP id h8JAClSX043431; Fri, 19 Sep 2003 11:12:47 +0100 (BST) From: Paul Richards To: "M. Warner Losh" In-Reply-To: <20030918.200249.63054367.imp@bsdimp.com> References: <1063802358.33631.44.camel@localhost> <20030918.200249.63054367.imp@bsdimp.com> Content-Type: text/plain Message-Id: <1063966391.33631.178.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Fri, 19 Sep 2003 10:13:12 +0000 Content-Transfer-Encoding: 7bit X-Sender-IP: 10.0.1.111 X-INT-DeliveryDone: h8JAClSX043431 cc: ports@freebsd.org cc: current@freebsd.org Subject: Re: Base packaging X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Sep 2003 10:13:09 -0000 On Fri, 2003-09-19 at 02:02, M. Warner Losh wrote: > Why would you want to package sbin? Where do you see this work going? > What problems do you think this will solve? Doing things a top level > directory at a time isn't very interesting, but since it looks like a > demo, perhaps you could sketch out what the polishing you'd envision. Well, as I mentioned in a followup. I'm actually doing this work so that I can use the system mk files for our product development, but I also wanted to be able to registered all the installed files from our products in the pkg db too. Having tried parallel trees, and hacking the ports mk files to get our code directly out of CVS and various other attempts eventually I found out that it's quite easy to link the two together, so that's what I did. So that's the problem it solves :-) I only chose sbin as a demo, you can put the PORTNAME entry in any Makefile and the granularity of the package it creates is going to be based on the content of the pkg-plist and not where in the tree the Makefile is. I'll reply to your other mail with specific points. Paul.