X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,SPF_HELO_PASS,TW_YG,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Achim Gratz Subject: Re: [ANNOUNCEMENT] Test update: perl-5.14.2-1, please update your dependent packages Date: Fri, 04 May 2012 07:32:55 +0200 Lines: 48 Message-ID: <87vckc33zs.fsf@Rainer.invalid> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1.50 (gnu/linux) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Reini Urban writes: >> 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. The build goes OK as well as the install. It is when I then use it from a very simple script (just perl -e 'require LWP qw( $ua request );' is enough actually) that things fall apart. Or trying to do the next build with cpan(m) which fails unless you let it fall back to curl or wget. I first thought the reason for this was that some parts were in site_per and the others in vendor_perl, but even when I symlinked the two the issue was not going away. >> 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. Tell me about it, that's why I've scripted it. Give it a list of module names and it gives you back the cygport files and initial setup.hint for each, with dependencies for build and install. For most modules that's all that was needed, but a handful did need patches, either because they needed extra configuration or tried to run manual tests. > I rather prefer only one single dependency and update step than 150. If all machines this installation is going to had internet access than cpanm would do the job, but I'll have to be able to install onto isolated machines. Anyway, I can understand if you're not wanting to go there, I can just not install perl_vendor and drop in a bundle package that pulls in the individual modules (or rather distributions, since cygport builds on them). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada -- 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