On Sunday, March 30, 2003, at 09:44 PM, Stas Bekman wrote:
Ken Williams wrote:
On Thursday, March 27, 2003, at 08:36 PM, Stas Bekman wrote:
+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
> in as fancy/complex a way.
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?
You can create and maintain the META.yml file yourself if you want. PAUSE isn't going to care who creates it.
That works for me. When the format of META.yml is going to be finalized and supported by PAUSE?
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?
I don't think difficulty is the issue. The issue is that people don't think that's a very good solution to the problem, and we're trying to come up with a better one.
Sure, that's cool with me. So far nobody I haven't heard the arguments against my proposal. But META.yml is quite similar to my proposal, though more general-purpose than mine.
What I'm afraid of, is that N moons from now the syntax of META.yml may change to incorporate things that weren't thought about earlier, whereas a simple file ala MANIFEST.SKIP seems like a more robust thing to me. I could be wrong.
__________________________________________________________________ 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
