Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 2050 invoked from network); 23 Apr 2002 01:21:21 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 23 Apr 2002 01:21:21 -0000 Received: (qmail 20048 invoked by uid 97); 23 Apr 2002 01:13:58 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 20031 invoked by uid 97); 23 Apr 2002 01:13:58 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 20009 invoked from network); 23 Apr 2002 01:13:57 -0000 From: "Conor MacNeill" To: "Ant Developers List" Subject: RE: RPMs (Was: Ant 1.5alpha refresh notice) Date: Tue, 23 Apr 2002 11:16:44 +1000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Importance: Normal In-Reply-To: X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > From: GOMEZ Henri [mailto:hgomez@slib.fr] > > >> What do you means by incorrect directory layout ? > > > >Ant scattered in three different dirs (I like the power of setting > >ANT_HOME). > > ant live in 3 differents dirs to respect rpm and fhs policies : > Are these policies documented anywhere? Just curious. > exec should go to /usr/bin > java jars goes in /usr/share/java or /usr/share/java/toolxxx/ > rpm doc should go in /usr/doc/toolxxxx/ (old RH/MDK) or > /usr/share/doc/toolxxx (recent MDK/RH) > > I agree but the ant script in jpackage is more sophisticated > and allow users to ant without jikes. > I don't know which script is better, but in the end it is a question of how we can support RPM users when they have problems with the script. Having a different script and different layout makes support harder. It also means you need to track changes, such as the introduction of ANT_ARGS variable. There are other problems, IMHO. The setting of ANT_HOME=/usr does not make sense. The lack of a real ANT_HOME causes a problem because some Ant tasks rely on auxillary scripts in ANT_HOME/bin (antRun) which are not included in the RPM and will break Ant in certain circumstances. Also a common way of making things available to Ant at runtime is to put them into ANT_HOME/lib. While this has well known shortcomings, it is also common advice, which will not work for an RPM user. When RPM building goes beyond simply packaging, there are certain dangers ... Conor -- To unsubscribe, e-mail: For additional commands, e-mail: