Subject: | Plugin silently doesn't add conflicts checking if [Conflicts] declaration appears too soon in dist.ini |
If [Conflicts] appears in dist.ini above [MakeMaker] or [ModuleBuild]
(or [@Basic], which includes [MakeMaker]), then there is no Makefile.PL
generated yet, so setup_installer() can't find any file to insert its
conflict checking code into - which means that the installation silently
gets no conflicts checking.
I'll be sending a patch which calls log_fatal if no *.PL file is patched
- I can't think of a good reason why the user would deliberately want to
circumvent this behaviour.