> Not quite trivial, with the way it all works. Maybe I can inject an > extra dependancy on the install target to do it...
In fact, not really. I've pushed up some changes that accomplish it, but it's not even remotely trivial, and is in fact terribly grody. Also fragile as heck, and subject to breakage in a number of ways in the future. I think we need to pick another course. There are two separate problems. The first is that it's failing to find the location, which really should be a vanishingly rare case, so something's off in the search process. I don't have even a glimmer of what, so I'm going to need help tracking that down. And really, with this fixed, #2 should be rare enough as to be totally ignorable. The second is that since the error only really effects itself at install time, erroring at all is pointless for people who will never install. With pushed changes, that's now sort of handled by only warning during the configuration, and saving the fatality until the install. That's more than a little bleh in itself for friendliness, but moves from ugly wart to gross hack from the contortions necessary to implement it, and how quickly it will stop even working at all due to things like rearranging the source tree. So, I think I'd prefer to back it out. With (1) fixed, it shouldn't become a question anyway, and in the extraordinary case that it does, you can just set MANBASE to /any/old/crap and it won't matter since you're not installing. -- Matthew Fuller (MF4839) | [email protected] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
