On Thursday, March 6, 2003, at 04:26 AM, [EMAIL PROTECTED] wrote:
On Tue, Mar 04, 2003 at 06:14:24PM +0100, Mattia Barbon wrote:I took me a long time to figure out why new users (with clean installs) couldn't get anything to work while the developers couldn't reproduce this behavior on seemingly identical systems (they ran the sub-Makes at some point). This required me to find out much more than I ever wanted to know about the inner-workings of MakeMaker. I think it would be really helpful to others to at least mention this in the documentation for 'DIR'. I know that would have saved me quite a bit of time.On Mon, 3 Mar 2003 22:58:12 -0500 Ilya Goldberg <[EMAIL PROTECTED]> wrote:
I think it is a (minor) bug.To answer my own question, the problem was a bug (feature?) in how 'DIR' is processed.
Yes, its a known bug. MakeMaker doesn't really recurse into sub-directories
properly. It only goes down one at a time. Its in the TODO list but I
won't be bothering to fix it. If someone wants to take a whack at it, sure.
Another solution is to put a Makefile.PL in each directory between the
root and the directory with the other Makefile.PLs. Example: if current
This seems to be the universal work-around.
This would require place-holder Makefile.PLs that don't actually make a package. The directories they would be in are chuck-full of sub-packages (classes in my case). What would one set 'NAME', etc to? It seemed a less-clean work-around to me than simply declaring INST_* as absolute paths in the top-level Makefile.PL. Do you think there may be a potential problem with this approach?
Thanks
Ilya
