Graham Barr [[EMAIL PROTECTED]] quoth: *>> Ideally, we would change what 'make dist' is doing now without asking *>> the user to do anything. *> *>Yes, I belive it should create the OSD file and include it, even though *>it is not specified in the MANIFEST. Maybe it should add it to the MANIFEST *>that is included if it is not specified in there already. It should be both unintrusive as well as easy to use for beginner and expert alike. This may be a good time to step back from the specific implementation details and ask 'What is the specific goal of this information?' or why do we want it, what problems will it solve and what benefits will we expect to reap from it? My only specific thought is that a library without a card catalogue is useless except for browsing as finding a book easily or at all is nearly impossible...and this reminds me of CPAN. Some form of index information contained in the module itself that can be tossed into a database would solve the growing muddle that is CPAN. If we can decide what information should be included first, the how will move along after that. What information should this metadata thingy contain? e.
