From owner-freebsd-java Tue Aug 27 3: 1:18 2002 Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 29E1237B401; Tue, 27 Aug 2002 03:01:16 -0700 (PDT) Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2906A43E75; Tue, 27 Aug 2002 03:01:14 -0700 (PDT) (envelope-from absinthe@pobox.com) Received: from dhcp068-64-151-24.nt01-c4.cpe.charter-ne.com ([24.151.64.68] helo=laredo.retrovertigo.com) by albatross.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 17jd9o-0000BN-00; Tue, 27 Aug 2002 03:01:08 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Dylan Carlson Reply-To: absinthe@pobox.com To: Ernst de Haan , Calvin Varney Subject: Re: Port/package guidelines (Ant) Date: Tue, 27 Aug 2002 06:01:27 -0400 User-Agent: KMail/1.4.2 Cc: freebsd-java@FreeBSD.ORG References: <200208170958.14422.absinthe@pobox.com> <200208220443.18447.absinthe@pobox.com> <200208262209.AAA07190@smtp.hccnet.nl> In-Reply-To: <200208262209.AAA07190@smtp.hccnet.nl> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200208270601.27637.absinthe@pobox.com> Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Monday 26 August 2002 06:09pm, Ernst de Haan wrote: > o An Ant-based port sets USE_ANT=YES which is interpreted by > bsd.java.mk. Agree. > o Should the port come with a build.xml file or should it set some > properties that will allow us to _generate_ a build.xml file for > it? Short-term, probably just ship it with a static build.xml. Then I'd say once we get sophisticated enough with Ant, we can build an XML out of bsd.java.mk based on variables set in the Makefile. Unless you think it's trivial enough to do the latter now. > o If the port comes with a build.xml file, then should it have some > default targets? "doc-install" target for those who want the JavaDocs built and installed. Other than that I can't think of any others (it may be too early in the day yet). One thing not mentioned about Ant (often) is that it works great with CVS. I was thinking that we could make "-devel" ports pull straight from CVS when available, instead of being locked in to a particular version. > o How do we install any JAR files, source code, Javadoc API documentation, > etc in a standard manner? Destinations for everything has been defined based on our earlier discussions _except_ for source code. I am assuming any source would be ${PREFIX}/src/${PORTNAME}/${PORTVERSION}. The real question is whether we want to have Ant run dependency checking instead of the pkg system. I think we do, my opinion is to turn over as much of the functionality to Ant as possible. The more it does the more effective it becomes. Cheers, -- Dylan Carlson [absinthe@pobox.com] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message