From: Thomas Wicklund <Tom.Wicklund@dothill.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Perl 5.14 and XML::Parser
Date: Thu, 23 Aug 2012 18:31:00 -0000 [thread overview]
Message-ID: <91D7F7CEBD3E804FA475882D8920476C281DB0E6AE@dc-ex1.power.com> (raw)
In-Reply-To: <CAHiT=DHJnEkcJxTmv2OaaAA50ws8TSV2iU8_uUTfXWD8Rhj+Eg@mail.gmail.com>
On Friday, August 17, 2012 4:50 PM, Reini Urban wrote:
>On Thu, Aug 16, 2012 at 6:55 AM, Christopher Faylor wrote:
>> On Wed, Aug 15, 2012 at 10:04:48PM -0600, Thomas Wicklund wrote:
>>>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."
>
>That was the short summary, yes.
>
>>>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 request from Yaakov and also from upstream p5p
>I have moved all non-core packages to the new perl_vendor.
>
>>>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.
>
>This is right. I really sympathize with you and all others.
>But unfortunately I had to made this move for political reasons,
>not technical ones.
Thank you for the response. While the new package was annoying and
took some time to figure out, I was more concerned that the
announcement implied that the new package was for modules which
weren't of general use.
I didn't see the original announcement (we rarely update cygwin) so it
took a while to find. However, even if I had seen the announcement I
wouldn't have had any reason think it would affect me.
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
prev parent reply other threads:[~2012-08-23 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 7:40 Thomas Wicklund
2012-08-16 7:41 ` Christopher Faylor
2012-08-18 0:45 ` Reini Urban
2012-08-23 18:31 ` Thomas Wicklund [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=91D7F7CEBD3E804FA475882D8920476C281DB0E6AE@dc-ex1.power.com \
--to=tom.wicklund@dothill.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).