> in as fancy/complex a way.
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 though not
it doesn't have to be fancy/complex. To my immediate need a file with explicit listing of all the files to be listed will suffice.
[...]
What happens to the modules which don't use Module::Build, but use EU::MM?
I need to release Apache::Test on CPAN and I can't do that, because of the bundling problem. I don't know how many man-months very spent on writing the current mod_perl 2.0's build, and while it'd be cool to move to Module::Build it'll take a *lot* of time.
Really, why that should be such a big problem to filter out files which are listed in a given skip list file?
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
