From owner-freebsd-ports@FreeBSD.ORG Sat Mar 6 02:33:44 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 602DA16A4CE for ; Sat, 6 Mar 2004 02:33:44 -0800 (PST) Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.131.111.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15DBD43D1F for ; Sat, 6 Mar 2004 02:33:44 -0800 (PST) (envelope-from gerald@pfeifer.com) Received: from [128.131.111.60] (acrux [128.131.111.60]) by vexpert.dbai.tuwien.ac.at (Postfix) with ESMTP id 76C0D13793; Sat, 6 Mar 2004 11:33:42 +0100 (CET) Date: Sat, 6 Mar 2004 11:33:44 +0100 (CET) From: Gerald Pfeifer To: Etienne Robillard In-Reply-To: <200402281119.11188.erob@videotron.ca> Message-ID: References: <200402271110.i1RBArT5061902@freefall.freebsd.org> <200402281119.11188.erob@videotron.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-ports@freebsd.org cc: Kris Kennaway Subject: Re: ports/63427: [lang/gcc33] Disabling the Java frontend at compile time X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2004 10:33:44 -0000 On Sat, 28 Feb 2004, Etienne Robillard wrote: > But in order to not break package building (make package), it need a way to > specify to not include (uninstalled) java files while doing the packing list. > I tried something like : > > post-install: > .if defined(WITHOUT_JAVA) > .for j in ${JAVA_BINARIES} gcj ... > (${ECHO_CMD} "@ignore_inst bin/${j}${SUFFIX}") >> ${TMPPLIST} > .endfor > .endif > > But that doesn't work with the current building process.. > Any clue on how to remove files from the plist ? Yes. ;-) In fact, I am currently working to fix the gcc ports on sparc and ia64, where libjava is not built. My plan is to add a knob, WITHOUT_LIBJAVA or similiar, which is enabled by default on these two platforms, and which you could then simply use for your purpose as well. Since I assume you are mostly worried about build time and size of the package, this might in fact be sufficient? (Building Java without libjava is comparatively cheap.) If it is not, you can simply extend the framework I'm going to add to also disable Java per se. Does that sound like a good plan? > Other possibilities to fix the plist may be to use a small perl script. Thus, > the script could be triggered like this: > EXTRA_PATCHES=${FILESDIR}/nojava_plist.pl We should try to avoid relying on Perl, as far as I understood. Gerald -- Gerald Pfeifer (Jerry) gerald@pfeifer.com http://www.pfeifer.com/gerald/