Preventing missing dependencies
aaron.trevena at gmail.com
Sun Feb 26 19:54:53 GMT 2006
On 26/02/06, Robin Berjon <robin.berjon at expway.fr> wrote:
> I've lived through the frustration you describe enough to agree that
> it's a good thing to fix it, but putting the onus on use seems wrong.
> I have quite a few modules that I don't intend to make CPAN-worthy,
> and that use other distribution mechanisms, and I wouldn't want to
> throw in a fake list of dependencies that I don't need just to work
> around what use would do. That's way too Java-ish.
> One thing that could be nice is to have this check in make dist (that
> is, in all modules that have some code run for make dist). It's a
> safe assumption that module authors want to fix missing dependencies,
> and will be happy to be warned that for the nth time they forgot to
> require DBI, LWP, or XML::SAX. I sure would be.
Surely make test rather than make dist - it should be relatively
simple to write a test, that checks dependancies against either
Makefile.PL or META.yaml.
I'm guessing there are all the required pieces on CPAN to knock
together a Test::PreRequsitites within a couple of hours
I'd certainly start to use it if was available - using make test
regularly during development makes my life a lot easier and any
automated tests like Pod::Test and Pod::Coverage I can throw in save a
lot of time.
More information about the london.pm