Due to the size of CPAN, all the module building is automated. Some of the build failures are due to this automated build process (e.g. you cannot automatically build a DBD-* driver without installing the client libraries for that database first). We try to add additional building instructions for popular modules that don't build automatically. But a lot of modules also fail their Makefile.PL or their tests when running unattended.
We started to make the build logs available on the Build Status pages so that authors can check for themselves why their module isn't included on our PPM repository. If it is a problem they can fix, then all they need to do is upload a new version to CPAN and it should appear automatically on the PPM repository within a few days.
We also host a PPM mailing list for any questions related to PPM in general, and to our repositories and the module building process in particular.
PS: The build status pages are not completely uptodate yet, as some of the results are from the time when the build logs didn't get published. A rolling rebuild should be complete soon to sync the logs up with the current status of the build engine.
In reply to Re: Re: Central PPM Repository?
by jand
in thread Central PPM Repository?
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |