delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2004/08/25/13:45:58

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Wed, 25 Aug 2004 13:45:46 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: "Gerrit P. Haase" <freeweb AT nyckelpiga DOT de>
cc: Gary Nielson <gary AT garynielson DOT com>, cygwin AT cygwin DOT com
Subject: Re: Cygwin-Perl upgrade and modules
In-Reply-To: <1331824927336.20040825133738@familiehaase.de>
Message-ID: <Pine.GSO.4.61.0408251344080.1589@slinky.cs.nyu.edu>
References: <200408250038 DOT i7P0c5Pg020485 AT ms-smtp-01-eri0 DOT southeast DOT rr DOT com> <1331824927336 DOT 20040825133738 AT familiehaase DOT de>
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.39

On Wed, 25 Aug 2004, Gerrit P. Haase wrote:

> Gary wrote:
> 
> > The other day, I decided to finally update all my cygwin packages with
> > setup.exe -- including perl. Went from 5.8.0 to 5.8.5 and now realize that
> > the path to all the modules I installed is under the older version at
> > /usr/lib/perl5/site_perl/5.8.0 instead of  /usr/lib/perl5/site_perl/5.8.5.
> > I've always shied away from upgrading perl in Linux so don't have much
> > experience dealing with modules from older installations. Must I re-install
> > all these modules, or can I add a path to them in my scripts, or should I
> > revert back to the older version of perl and if so, how? Any help
> > appreciated.
> 
> It is not binary compatible (IIRC, 5.8.0 was not threaded), so you
> should recompile all modules which require compilation, pure perl
> modules may be moved from 5.8.0 to 5.8.5 path, however I always rebuild
> them from scratch. 
> 
> The autobundle command in a CPAN shell is meant to create a list of
> packages which you have installed (run before unistalling), after update
> you may simply run `install autobundle_$date` in the CPAN shell, this
> pulls all listed modules and tries to install it.
> 
> 
> Gerrit

Gerrit,

Would it make sense to always run the autobundle CPAN command in the perl 
preremove script?  This way, the list will be available for the 
postinstall script or a (recently proposed) migration assistance script to 
do what it will.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Happiness lies in being privileged to work hard for long hours in doing
whatever you think is worth doing."  -- Dr. Jubal Harshaw

--
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019