Hi,
Am Dienstag, 16. September 2003 09:38 schrieb Stas Bekman:
Boris Zentner wrote:
Hi,
Am Freitag, 12. September 2003 20:04 schrieb Stas Bekman:
[redirecting it to the httpd-test dev list where this discussion belongs]
Boris Zentner wrote:
Hi Stas,
I spend the morning on porting Apache::PageKit to Apache::Test and make the installation of this large module easy. My idea to support perl < 5.8 and >= 5.8 was to use patch inside the makefile and make the changes to my files after they are copied to the blib directory. So the original files are avail everytime. Im not really sure if this is a good way, but it stopped working on the 'make test' part since on some configurations the content of Apache-PageKit/lib is not the same as Apache-PageKit/blib but Apache::Test use Apache-PageKit/lib instead Apache-PageKit/blib. I think this is wrong since if all goes well I install the content of Apache-PageKit/blib and this is not what I tested.
I attach a patch that fix it for me. The above comment seems also misleading.
The idea is to allow developers to test against the live files under lib, to make it possible to develop while running the test suite. I use this feature all the time in combination with Apache::Reload. You are right that we want to test against the blib when users run 'make test'. Purhaps we should make it configurable, so it's not hardwired? e.g. we could have an environment variable APACHE_TEST_DEV_MODE which when set will add the non-blib dirs to @INC.
I'm happy with the ENV idea; but i fail to see, why a lib after the blib spoil your work with Apache::Reload since under normal development, there is no blib directory.
what do you mean normal development? Once you run 'make' you get 'blib'. I develop now inside the source distro and test on the place. Apache::Test rules.
I was under the impression of the commet directly over the fix that the 'lib' was the lib inside mod_perl ( or that was the desired lib, sure I noticed that the real world and the comment do not match ).
So my conclusion was that you work inside the perl/lib or mod_perl/lib and not inside your project directory.
I guess it's late, but I fail to follow your logic here. All I want is project/lib to be the very first in @INC. that's for dev of course. I develop inside the project directory.
If possible I prefer a automatic solution.
what do you mean? AI ;)
That whould be fine with me too ;-) But now that I understand your prefered development strategy. I agree that the the best solution is the ENV var.
Cool, we can also have a command line flag. [...]
That would be so cool! I can not agree more. Thank you.
Have a nice day.
night for me, but a good day to you too ;)
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
