Cygwin-Perl upgrade and modules

Wed Aug 25 20:02:00 GMT 2004

On 2004年8月25日, 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@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_		igor@watson.ibm.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/