X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.9 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_YG X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: Date: Thu, 3 May 2012 10:48:33 -0500 Message-ID: Subject: Re: [ANNOUNCEMENT] Test update: perl-5.14.2-1, please update your dependent packages From: Reini Urban To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id q43FnFN0006902 On Thu, May 3, 2012 at 9:24 AM, Achim Gratz wrote: > Reini Urban x-ray.at> writes: >> perl has been updated to 5.14.2-1 as test in the Experimental section. >> >> It looks pretty stable to me when I tested it in the last 2 weeks. > > I've hit two interesting snags (perl_vendor is installed): > > 1) Some modules, when built with cpanminus fail at test, but the same module > built with cpan tests OK (File::Slurp being the most simple example I have right > now). Interesting. I'll look into that. I regularly try out cpanm also. I thought we only got problems with Module::Install and Module::Build cs. EUMM. > 2) If I install another module that uses LWP (HTTP::Status, for example), then I > also need to reinstall LWP.  Otherwise I'm getting errors like these: > > Attempt to reload LWP/Protocol/http.pm aborted. > Compilation failed in require at (eval 7) line 2. I could not repro this. I built HTTP::Status just fine. I'll think about it. > Lastly, I'd much prefer if the vendor modules would be separate entities to > install, this would make it easier to keep proper dependencies among them.  I > will re-build all these modules plus some 150 more with cygport anyway (provided > I don't hit a roadblock), so once that works I could send you the perl-*.cygport > files. Sorry, too much manual work. I rather prefer only one single dependency and update step than 150. These are just the basics to get CPAN and CPAN::Reporter working, the rest you can do by your own. You''l only need such cygports deps (like Yaakov needs them) if you build projects requiring perl modules. There are not many. -- Reini Urban http://cpanel.net/   http://www.perl-compiler.org/ -- 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