From owner-freebsd-current@FreeBSD.ORG Thu Sep 18 03:28:17 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 512B716A4B3; Thu, 18 Sep 2003 03:28:17 -0700 (PDT) Received: from hardy.inty.net (hardy.inty.net [195.224.93.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id A47BE43FD7; Thu, 18 Sep 2003 03:28:15 -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 hardy.inty.net (8.12.9/8.12.9) with ESMTP id h8IAS9FO056656; Thu, 18 Sep 2003 11:28:10 +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 h8IAS8SX061280; Thu, 18 Sep 2003 11:28:08 +0100 (BST) From: Paul Richards To: Alexander Leidinger In-Reply-To: <20030918122510.50ea84c3.Alexander@Leidinger.net> References: <200309171445.h8HEjrh6065898@grimreaper.grondar.org> <1063812422.33631.104.camel@localhost> <20030918122510.50ea84c3.Alexander@Leidinger.net> Content-Type: text/plain Message-Id: <1063880911.33631.150.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Thu, 18 Sep 2003 11:28:31 +0100 Content-Transfer-Encoding: 7bit X-Sender-IP: 10.0.1.111 X-INT-DeliveryDone: h8IAS8SX061280 cc: ports@freebsd.org cc: current@freebsd.org cc: Mark Murray 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: Thu, 18 Sep 2003 10:28:17 -0000 On Thu, 2003-09-18 at 11:25, Alexander Leidinger wrote: > On Wed, 17 Sep 2003 16:27:03 +0100 > Paul Richards wrote: > > > > However, I suspect that a marginally better place to use these would be > > > in the "make distribute" target that "make release" uses. This way, the > > > files are already separated out into directory structures, and it may be > > > easier to build complex pkg-plist's with find(1). ALSO, it may be easier > > > to make more fine-grained packages (DISTRIBUTION=foo) with this. > > > > I looked into this originally so that I could use the standard BSD make > > includes for a project in work but I needed some way to have "install" > > wrappered so that any files installed by my project were registered in a > > package. Therefore, I wouldn't want it restricted to just FreeBSD > > release scripts since I want to be able to use it outside of the FreeBSD > > tree. > > We have programs in the ports tree which use our bsd.*.mk > infrastructure. Will there be a problem if such a program gets installed > from ports (will it try to register itself 2 times)? I don't know, have you got an example port I can look at? Paul.