From owner-freebsd-current Wed Apr 22 00:03:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10654 for freebsd-current-outgoing; Wed, 22 Apr 1998 00:03:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10644 for ; Wed, 22 Apr 1998 07:03:05 GMT (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id JAA02461; Wed, 22 Apr 1998 09:02:56 +0200 (CEST) To: Harlan Stenn Cc: current@FreeBSD.ORG Subject: Re: bin/6353 In-reply-to: Your message of "Wed, 22 Apr 1998 02:45:46 EDT." <12590.893227546@brown.pfcs.com> Date: Wed, 22 Apr 1998 09:02:56 +0200 Message-ID: <2459.893228576@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <12590.893227546@brown.pfcs.com>, Harlan Stenn writes: >What needs to be done to contributize it? > >I hope it doesn't involve converting it from auto*/configure to bmake... [talking about the new "am-utils" version of amd and of upgrading] Well, Uhm, Sort of... The idea is to stick it unmodfied under src/contrib/am-utils and make a scaffold makefile in src/usr.sbin/am-utils which does all the right things for our build targets. You can see examples of this in various other programs (awk, bind, bison and so on..) The alternative is to kill amd and make am-utils a port instead I think I prefer the alternative, what do the good people on -current say ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message