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: <3D077E5A.1000905@ece.gatech.edu> Date: Wed, 12 Jun 2002 13:01:14 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 Newsgroups: gmane.os.cygwin To: "Gerrit P. Haase" CC: "'cygwin@cygwin.com'" Subject: Re: How to simplify cygwin+perl application deployment References: <58460277113.20020612171342@familiehaase.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Gerrit P. Haase wrote: > Should be also no problem to bundle > single modules for individual setup. Not entirely true. There is a database file 'perllocal.pod' within /usr/lib/perl5/5.6.1/ that must be updated by the perlmake install process. It's best to not update this file at all, if you are creating perl modules that others will install. You can skip the 'update perllocal.pod' step by doing 'make pureinstall' -- this is what I did back when I was packaging perl modules as RPMS for perl5.005_62-cygwinb20-991109. I used the makerpm.pl script (slightly modified) to turn each perl module into an rpm. Of course, you need rpm.exe for this to work...which is not yet available as a standard cygwin package. You can get makerpm.pl here: http://www.neuro.gatech.edu/users/cwilson/cygutils/perl-contrib/index.html --Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/