I did send the patch to Matt couple of days ago, but haven't heard back yet.
I suppose I can also brace myslef, add namespaces, and clean up my own code. As for the versioning, if this patch could be useful in both mod_perl 1.* and 2.0, can it be applied to both distributions? I don't quite understand why installing Apache::Reload from CPAN will cause mod_perl2.0 to be installed, but I'll try to think some more about it. Stas Bekman wrote: > Harry Danilevsky wrote: > >> I certainly agree with attaching a common prefix to a library, but >> what if I am already dealing >> with a bunch of modules written without prefix, and enough >> application code using those packages ? >> I suppose I could change the code, or alias names in symbol table, or >> do some other trick; >> I just figured that one extra directive, plus one patched line was a >> cheap solution to my >> problems. >> >> I guess if nobody else sees any value in it, I'll just keep the >> private patched version for myself :-) > > > No, no, I was asking whether you can re-use the existing options > without adding new ones. Nobody has asked for this feature since the > package was created. It certainly has a value. e.g. you may want to > watch only Apache:: packages from a certain private directory. > > I guess you should send the patch to Matt and I'll sync the version in > mod_perl 2.0 (CC me). Though we need to figure out how to resolve the > versioning conflict. so when you ask for Apache::Reload from CPAN.pm, > it won't install mod_perl 2.0. Ideas? >
