Re: Cygwin-Perl upgrade and modules
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/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,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/
Re: Cygwin-Perl upgrade and modules
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. E.g. when you start setup.exe as user A, which is your Cygwin HOME path then? 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. Maybe it is worth to have it as a standalone package though? Gerrit -- =^..^= http://nyckelpiga.de/donate.html -- 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/
Re: Cygwin-Perl upgrade and modules
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/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,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/
Re: Cygwin-Perl upgrade and modules
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 -- =^..^= http://nyckelpiga.de/donate.html -- 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/
Re: Cygwin-Perl upgrade and modules
On Tue, Aug 24, 2004 at 08:38:09PM -0400, Gary Nielson 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. For perl in general, versions from 5.8.2 to 5.8.5 are supposed to have backward compatibility with 5.8.0-built modules. However, the cygwin perl 5.8.0 was non-threaded and the cygwin perl 5.8.2 and 5.8.5 are threaded, which makes them incompatible, so any xs modules will need to be reinstalled. The CPAN autobundle command is supposed to provide a fairly easy way to do this, but I haven't used it myself (and you need to do it before uninstalling 5.8.0.) I think the last 5.8.0 package was named perl-5.8.0-5.tar.bz2. Try googling for that filename to see if it is available somewhere on a stale mirror. -- 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/
Re: Cygwin-Perl upgrade and modules
At 08:38 PM 8/24/2004, you 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. Isn't this a Perl rather than a Cygwin question? Forgive me. Maybe I'm wrong. I have to admit a shameful naivete when it comes to Perl. :-( -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/
Cygwin-Perl upgrade and modules
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. -- Gary -- 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/
