Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: cygwin@cygwin.com
Path: not-for-mail
From: Charles Wilson <cwilson@ece.gatech.edu>
Newsgroups: gmane.os.cygwin
Subject: Re: How to simplify cygwin+perl application deployment
Date: Wed, 12 Jun 2002 13:01:14 -0400
Lines: 22
Message-ID: <3D077E5A.1000905@ece.gatech.edu>
References: <58460277113.20020612171342@familiehaase.de>
NNTP-Posting-Host: 1cust227.tnt11.atl4.da.uu.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Date: Wed, 12 Jun 2002 17:01:04 +0000 (UTC)
Cc: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2

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/