From owner-freebsd-perl@FreeBSD.ORG Thu May 10 00:08:12 2012 Return-Path: Delivered-To: perl@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 09F50106566B for ; Thu, 10 May 2012 00:08:12 +0000 (UTC) (envelope-from milki@rescomp.berkeley.edu) Received: from hal.rescomp.berkeley.edu (hal.Rescomp.Berkeley.EDU [169.229.70.150]) by mx1.freebsd.org (Postfix) with ESMTP id E81B88FC0A for ; Thu, 10 May 2012 00:08:11 +0000 (UTC) Received: by hal.rescomp.berkeley.edu (Postfix, from userid 1070) id 68993119D66; Wed, 9 May 2012 17:08:11 -0700 (PDT) Date: Wed, 9 May 2012 17:08:11 -0700 From: milki To: perl@freebsd.org Message-ID: <20120510000811.GC15329@hal.rescomp.berkeley.edu> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="zYM0uCDKw75PZbzx" Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: p5-XML-SAX non-interactive patch proposal X-BeenThere: freebsd-perl@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: maintainer of a number of perl-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 May 2012 00:08:12 -0000 --zYM0uCDKw75PZbzx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline The p5-XML-SAX-0.99 includes an interactive prompt on package install. The attached patch moves that choice into an OPTIONs. It also removed ParserDetails.ini from the pkg-list. This does not deal with the issues with p5-XML-SAX-Base. >From a glance, it appears that ParserDetails.ini lists available parsers for XML::SAX. This interactive option allows the user to update the XML::SAX::PurePerl entry in the file. Note: There are still issues with how this ParsersDetails.ini is updated/created which I open to others to fix... Basically: - If XML::SAX has already been installed, there should be an existing ParsersDetails.ini. The port install should update the file. - Otherwise, - The file might exist anyways in @INC, in which case it should be updated - Else, it should be created If the port is freshly installed out of PREFIX, the install will fail because it won't find XML::SAX in @INC (running port test). If the port is installed (different PREFIX) side-by-side an existing install, the existing ParsersDetail.ini will be updated instead of creating a new one in the different PREFIX. -- milki --zYM0uCDKw75PZbzx--