Re^2: Dealing with XS modules on multiple platforms

in reply to Re: Dealing with XS modules on multiple platforms
in thread Dealing with XS modules on multiple platforms

Thanks for this. I like the idea of running a local CPAN repository to take care of hacks (and versions). I have a feeling I can do this so that the local repository just goes to a real one if it can't find what it's been asked to build. We could potentially then use a Module::Install script to make it easier to allow for a re-build for a new platform.

It still means I'd have to maintain a separate dir of built modules for each platform, but not sure there's an easy way around that.

Comment on Re^2: Dealing with XS modules on multiple platforms

Replies are listed 'Best First'.
Re^3: Dealing with XS modules on multiple platforms by Corion (Patriarch) on Jul 24, 2008 at 12:28 UTC
Also see CPAN::Mini and CPAN::Inject for creating/keeping the local mirror and the "distroprefs" feature of CPAN.pm for maintaining your local patches integrated in your mirror and automatically patching any module upon build time.	[reply]
Re^4: Dealing with XS modules on multiple platforms by moritz (Cardinal) on Jul 24, 2008 at 12:46 UTC
Just as a data point: my CPAN::Mini mirror uses less then 1GB of disk space (currently 866MB), because it keeps only one version of each distribution. 1GB shouldn't be a problem with today's disk prices ;-)	[reply]

In Section Seekers of Perl Wisdom