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 14:48:18 -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: cygwin AT cygwin DOT com, Gary Nielson <gary AT garynielson DOT com>
Subject: Re: Cygwin-Perl upgrade and modules
In-Reply-To: <1021848257393.20040825200628@familiehaase.de>
Message-ID: <Pine.GSO.4.61.0408251437520.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> <Pine DOT GSO DOT 4 DOT 61 DOT 0408251344080 DOT 1589 AT slinky DOT cs DOT nyu DOT edu> <1021848257393 DOT 20040825200628 AT familiehaase DOT de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Scanned-By: MIMEDefang 2.39

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

> Igor wrote:
> 
> >> 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
> 
> No, I think CPAN is interactive and it may fail.

Hmm, wouldn't "perl -MCPAN -e autobundle" work non-interactively?  The 
"install Bundle::my_bundle" may be interactive, but that won't be done by 
the preremove script, and can be configured to minimize the interactivity.

> E.g. when you start setup.exe as user A, which is your Cygwin HOME path 
> then?

Ah, but you can set "cpan_home", "build_dir", etc to be user-independent.  
Also, you can set "inactivity_timeout" and "prerequisites_policy" to avoid 
a lot of the interactivity.

> It may be needed to create this path additional to create files when you 
> want to uninstall perl, oh yeah, this was just the first point which 
> came to my mind when I think about it.  I don't want to say that it is 
> not possible to do this, you may write such a preremove script, however 
> I think perl users are programmers anyway and may well take care of 
> their own.

True, but it would be nice to be able to just say "migrate-perl-modules", 
or something, after upgrading perl, and have it mostly work...  I upgraded 
perl recently, and it was a bit of a pain, especially if one forgets to 
run autobundle before the upgrade (hence the recommendation of doing that 
in the preremove script).

> Maybe it is worth to have it as a standalone package though?
> 
> Gerrit

If it's in a standalone package, the preremove script will need to be 
named "perl-something" to get it to run when "perl" is uninstalled.  This 
poses two problems: one is that setup may do sanity checking in the future 
to only allow preremove scripts named after their respective packages, and 
two is that you may want to add a perl preremove script later, and there 
will be a clash.
	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/