X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=4.3 required=5.0 tests=AWL,BAYES_40,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org From: Thomas Wicklund To: "cygwin@cygwin.com" Date: Wed, 15 Aug 2012 22:04:48 -0600 Subject: Perl 5.14 and XML::Parser Message-ID: <91D7F7CEBD3E804FA475882D8920476C281DA3E6DE@dc-ex1.power.com> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id q7G46Vaw012595 The update of perl on to 5.14 moved some perl modules to a new perl_vendor package which is not installed by default. The announcement I found stated that perl_vendor is modules "which are mainly required to build and test and report test results of other CPAN modules." I find that the XML::Parser module (at least) has been moved. I've been using this module for years to parse XML output for a set of Subversion tools. I had a couple hours of digging today to figure out why a coworker started getting errors after updating Cygwin, then figuring out the new package. As an occasional user of perl I would much prefer that the maximum number of packages be included in the distribution (since disk space and bandwidth are constantly becoming cheaper) than to have to spend time figuring out why something can't be found. Thomas Wicklund -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple