I tried installing ActivePerl 5.10 back toward the beginning of the year,
but immediately reverted to 5.8 because I didn't have time to build
everything that was missing from PPM just to keep my production software
working.
Just this week I received what is intended to become my new development
platform, a Lenovo ThinkPad W500 with 8GB RAM running Windows Vista Business
x64 SP1. I blissfully installed ActivePerl-5.8.8.824-MSWin32-x64-287188,
expecting my development life to become even more joyful than
before...WRONG!
First off, I had to re-learn PPM command line arcanities since there is no
PPM GUI for x64. Then, once I had gotten back into the command line groove,
all of the repositories I've used in the past -- including ActiveState's,
which at least appears to be adjusted to look for 64-bit packages given its
URL: http://ppm4.activestate.com/MSWin32-x64/5.8/824/package.xml; (does
MSWin32-x64 seem oxymoronic to anyone besides me?) -- return zero
available packages.
So where do I go from here in order to waste the minimum amount of time? Am
I doing something wrong in PPM regarding the repositories? Should I install
5.8 32-bit? Should I try 5.10 64-bit? Perhaps I'm setting the bar too
high, but I would very much like to have my development cake and eat it
too
Thank you,
-Brian
-Original Message-
From: activeperl-boun...@listserv.activestate.com
[mailto:activeperl-boun...@listserv.activestate.com] On Behalf Of Jan Dubois
Sent: Monday, November 10, 2008 11:29
To: activep...@listserv.activestate.com;
perl-win32-users@listserv.ActiveState.com; p...@listserv.activestate.com
Subject: RE: PPM build servers are dead -- long live PPM!
The new PPM repositories are now the default repositories for all PPM4
releases (ActivePerl build 818 and later for Perl 5.8, all builds of
ActivePerl 5.10). There is nothing you have to do to enable them; they
have been moved on the server side to replace the old repos.
There are significantly more modules available for all platforms now,
including a full complement of 64-bit modules for Perl 5.10 (with the
Solaris 64-bit build limping behind a little bit).
If you find any problems, or have any kind of feedback, please file
a bug, send email to the PPM mailing list, or let me know directly.
Cheers,
-Jan
PS: If for whatever reason you need to refer back to the old repository
build status tables, they are still accessible through this link:
http://ppm.activestate.com/index.html
Those repositories and tables are static and unsupported and only
exist to allow exploratory work in case a module used to be included
in the old repo but didn't build for the new one.
On Sun, 22 Jun 2008, Jan Dubois wrote:
Our PPM build server infrastructure has been very maintenance
intensive; it needed some manual tweaking and fixing on a weekly
basis. We finally couldn't stand doing it any longer and turned them
off a couple of weeks ago. The PPM repositories are still there, but
they are not being updated anymore.
But fear not! We took the time saved from having to do all the build
monitoring and fixing and started writing a new simplified build
system that avoids many of the problems the old one runs into.
We have built test repositories for 32-bit ActivePerl 5.10 on Windows
and Linux and would welcome any feedback from people willing to
beta-test them. They are currently being hosted at:
http://ppm.activestate.com/beta
There you'll find additional information about configuring them as
your default PPM4 repositories. It contains links to the build-status
tables at the bottom (one per letter), e.g.
http://ppm.activestate.com/beta/idx/W.html
If you are a CPAN author then you will also want to check the status
page listing all the modules from your CPAN directory, e.g.
http://ppm.activestate.com/beta/author/GAAS.html
We are interested in feedback, especially regarding:
* Do you experience any problems with either the commandline or the
GUI PPM client with these new repositories?
* Do the modules installed from these repositories work properly on
your system? Did they fetch all necessary prerequisites?
* If you are a module author and your module did not build or test
properly: do the build logs contain sufficient information to
understand _why_ they were not being built?
* Is there any information that you would like to see in the build
status results? What is it, and what do you need it for?
Please send your feedback to the PPM mailing list at
mailto:p...@activestate.com
or enter a bug report in our bug database (use ActivePerl product
and PPM_Server component):
http://bugs.activestate.com/enter_bug.cgi?product=ActivePerl
Here are a couple of known issues that we are already aware of:
* Some packages contain additional files that are not needed (and
ignored) by the PPM client (HTML documentation, debugging symbols).
This has already been fixed
