On Nov 12, 2007, at 3:30 AM, Eric Wilhelm wrote:
The only actual requirement is that the version number be set in some package name which matches the filepath relative to Build.PL
That doesn't jibe very well with the module case - otherwise we'd all be setting variables like $lib::Module::Build::VERSION .
In other words, 'bin' is not part of the name of the script, it's just where the script lives by default. I would rather do "program_name => 'foo'" and have it look for 'foo' in script/ .
program_name => 'bin/foo'; Would expect $bin::foo::VERSION and give you a 'bin-foo-v0.0.1.tar.gz' tarball.
Here too I think 'bin' shouldn't be present. What if you decide you want to offload some of the code from the 'foo' script into a module in lib/? And then expose some of the guts with APIs? The 'bin' moniker isn't really appropriate anymore.
-Ken
