On Thursday, March 27, 2003, at 08:36 PM, Stas Bekman wrote: > The more I think about it the more I like my latest idea. I'm going to > expand on it in this post as I think it may do more things than just > solving the bundling problem. > > What I'm proposing is to have a mechanism similar to /robots.txt in > the HTTP protocol, where '/' is the root of the web server namespace > So now we have "the CPAN indexer protocol" and we introduce /INDEX, > where / is the top-level directory of a given package. > > /INDEX provides a way for a package to tell the indexer what it wants > to be exposed and/or what not. We can work out a simple syntax, like: > > +lib/ # expose all packages under lib/ > -lib/private.pm # but exclude lib/private.pm > +lib2/Foo.pm # expose lib2/Foo.pm Module::Build may soon do something like this, though not in as fancy/complex a way. In the META.yml file, we may start listing all the modules, with their versions and files, so that the CPAN indexer doesn't have to scan through the distribution to figure it out. If the indexer is willing to take this list as truth and not double-check it, would this solve your problem? Note that this solution isn't specific to Module::Build, it just relies on using a META.yml description file. -KenThread Previous | Thread Next