Re^2: Experience with ActivePerl 5.10 vs. 5.8 PPM incompability

Thanks NaN :) -
I've got :
... ActivePerl v.5.8.8.822
... PPM v. 4.02, 2007 ActiveState SW. Inc.

c:\ppm install PPM-Profile
installs :
... C:\Perl\site\bin\ppmprofile.pl
... C:\Perl\site\bin\ppmprofile.bat
... C:\Perl\html\bin\ppmprofile.html

C:\Perl\site\bin>ppmprofile save C:\profile.xml
ppmprofile.bat save is not supported for PPM4 yet at ppmprofile.bat line 94.

cat ppmprofile.bat :

.
.
91 sub save {
92    my $profile = shift @ARGV || 'profile.xml';
93    
94    die "$0 save is not supported for PPM4 yet" if PPM4;
95
96    open(my $fh, ">", $profile)
97      || die "Can't open profile file:" . "$profile ($!)";
.
.
[download]

OOps, seems my version of PPM doesn't support ppmprofile save / restore ... So I guess i'll have to try the other option in Upgrading from ActivePerl 5.8.x.

... 1 Use Window's Add / Remove Programs applet (accessible from the Control Panel) to uninstall ActivePerl.
... 2 Manually delete all directories beneath the Perl installation directory (by default C:\Perl) except the site\lib directory.
... 3 Install ActivePerl to the same directory (i.e., C:\Perl).
... 4 Use the ppm upgrade command to check for module updates.

Has anyone tried that yet ?
Best regards /
allan

Comment on Re^2: Experience with ActivePerl 5.10 vs. 5.8 PPM incompability Download Code

Replies are listed 'Best First'.
Re^3: Experience with ActivePerl 5.10 vs. 5.8 PPM incompability by Not_a_Number (Prior) on Jan 06, 2008 at 19:17 UTC
Hmm, I have the same problem: `ppmprofile.bat save is not supported for PPM4 yet...` Here's what I intend to try as a workaround when I upgrade to 5.10. Any suggestions for improvement welcome. (1) At the command line, run this command: `ppm list --fields name > C:/my_modules.txt` (2) Uninstall 5.8, install 5.10 (as per the ActiveState instructions that you quote). (3) Run the following script: `open my $fh, '<', 'C:/my_modules.txt' or die "Oops: $!\n"; while ( <$fh> ) { chomp; print "Installing $_...\n"; system ( "ppm", "install", $_ ); }` [download] A bit of a kludge? but better than trying to do the whole thing manually???	[reply] [d/l] [select]
Re^4: Experience with ActivePerl 5.10 vs. 5.8 PPM incompability by ady (Deacon) on Jan 06, 2008 at 20:26 UTC
I proceeded along the other path, as pr. the ActiveState instructions. The ppm upgrade resulted in a number of 'ordering conflicts', which I was able to resolve using the AS PPM application to reinstall the packages in question : C:\Perl>ppm upgrade ppm upgrade failed: No ordering between package Perl6-Currying-0.05 and Perl6-Currying ppm upgrade failed: No ordering between package Term-ReadLine-Perl-1.0302 and Term-ReadLine-Perl ppm upgrade failed: No ordering between package libwww-perl-5.808 and libwww-perl ppm upgrade failed: No ordering between package psh-1.8.1 and psh ppm upgrade failed: No ordering between package Digest-MD4-1.5 and Digest-MD4-1.5-r1 These ordering conflicts are probably a result of not having cleaned up obsolete ppm versions before reinstalling new ones; I can't blame that on the AS upgrade procedure as such After a succesfull ppm upgrade, there were still a number of 5.8 packages missing in the 5.10 upgrade installation (eg. Win32, Win32-IE-Mechanize, GD and others). These - it seems - are not (yet) included in the AS repository, and will have to be installed from other ppm repositories in the Perl community. The problem here is, that these ppms are not (yet) 5.10 'compliant'... At this point in the procedure I chose to 'fall back' on a 5.8 installation (I had done a backup of the Perl 5.8 \site \lib, \bin and \html directories :). I think I'll aim at installing 5.10 in parallel with 5.8 (as recommended above by fellow reverend monks), and use 5.10 for future projects, as the needed ppm-packages get available for the latest Perl. Allan	[reply]
Re^3: Experience with ActivePerl 5.10 vs. 5.8 PPM incompability by syphilis (Archbishop) on Jan 06, 2008 at 22:52 UTC
So I guess i'll have to try the other option in Upgrading from ActivePerl 5.8.x No - those instructions relate to upgrading from one version of perl 5.8.x to a more recent version of perl 5.8.x. But they don't apply to upgrading from 5.8.x to 5.10.x. In step 2, the site/lib directory also needs to be deleted since it could (and almost certainly would) contain modules that are binary-incompatible with 5.10. Cheers, Rob	[reply]