Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 20:06:28 +0200 From: "Gerrit P. Haase" Reply-To: "Gerrit P. Haase" Organization: Esse keine toten Tiere Message-ID: <1021848257393.20040825200628@familiehaase.de> To: Igor Pechtchanski CC: cygwin AT cygwin DOT com, Gary Nielson Subject: Re: Cygwin-Perl upgrade and modules In-Reply-To: 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 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit 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/