On 16 April 2010 14:38, Steve Bertrand <st...@ibctech.ca> wrote: > On 2010.04.16 09:15, Philip Potter wrote: >> What are you *actually* >> trying to do? What are you testing and why does this test require you >> to print output to the user under "make test"? > > This particular test: > > - checks to see if an existing installation of the project exists > - if yes, it reads both the currently installed config file, and the > default config file in the source tree > - it compares version numbers > - it collects all sections and directives from both files > - if versions differ, it informs the user that this is an upgrade > - if directives have changed, it informs the user which ones have been > added, and which ones have been removed > > I don't want to merge the configuration files, I just want the user to > be informed of what exactly they need to change. > > 'make test' does not provide the ability to print out individual > statements like prove does (from what I can tell). As I said, I think my > approach is wrong, and I need to move this code out of the test.
'make test' is for running a suite of tests in an automated fashion, so it's not designed to be easy to produce interactive output. It sounds like your test isn't a test, it's a setup tool. Tests in projdir/t are there to test if the stuff in projdir/lib or projdir/blib works, and shouldn't be dependent on what's already on your system other than ordinary module dependencies. I'm afraid this is beyond my skill level, but I'm sure it's possible to get EU::MM to report to the user when they try to install a new module over an old one. Sorry I can't be more help :( Phil -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
