Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Message-ID: <42239270.60205@familiehaase.de> Date: Mon, 28 Feb 2005 22:51:44 +0100 From: "Gerrit P. Haase" Organization: Esse keine toten Tiere User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.7.3) Gecko/20040910 MIME-Version: 1.0 To: john@morrison.mine.nu CC: cygwin@cygwin.com Subject: Re: (RESOLVED) Re: Installing Perl modules with "perl -MCPAN -e shell; " fails with "02packages.details.txt.gz does not contain a Line-Count header" References: <0MKpV6-1D4XMu3JLa-0001jh@mxeu1.kundenserver.de> <421F1B6A.10707@gtt-technologies.de> <422219B7.9030800@familiehaase.de> <42230C6D.2050702@gtt-technologies.de> <58969.84.246.168.11.1109595947.squirrel@mail.morrison.mine.nu> In-Reply-To: <58969.84.246.168.11.1109595947.squirrel@mail.morrison.mine.nu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes John Morrison wrote: > On Mon, February 28, 2005 12:19 pm, Stephan Petersen said: > >>Hi Gerrit, >> >>thanks for your and all the others' replies. >> >> >>>- The CPAN repository and build directory *must* reside in a path >>> mounted in binmode: >>> >>> mount -s -b -f c:/cygwin/home/username/.cpan /home/username/.cpan >>> mount -u -b -f c:/cygwin/home/username/.cpan /home/username/.cpan >> > > Could something along these lines be done in the postinstall for perl? > (Only if the mount doesn't exist of cause...) The user may want to use a different directory as repository and build directory. It should be done during the initial configuration, however I'm not sure if is worth the time to implement it. Since there are two or three rreports about this issue in a year shows that Joe User is actually reading the README *or* is not using textmode mounts. Anyway: PTA, Gerrit -- =^..^= -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/