# from Johan Vromans
# on Monday 12 November 2007 05:05:
> program_name => 'bin::foo';
Well, that is analogous to our existing 'module_name' parameter usage.
But, actually: not workable. If we have 'cgi-bin/foo', the substition
is one-way, so 'cgi_bin::foo' becomes ambiguous (not that we need to
save room for usage of a cgi_bin directory, just that the information
loss makes my spidey-sense tingle.)
>which can be shortened to the most elegant form:
>
> program => 'foo';
I don't think we can go there without assuming 'bin/' and blocking
ourselves out of using the 'script/' directory, not to mention
'cgi-bin' and sbin. The alternative would involve searching, or
declaring another term.
So, I'm going to stick with the file path. This can be reliably and
unambiguously translated to the distro or package name.
program_name => 'cgi-bin/foo-bar'
Would be package: cgi_bin::foo_bar, distro: cgi_bin-foo_bar.
Yes, this prevents the distribution built with the 'cgi_bin/foo_bar'
file, but I'm happy with that.
> a perfectly valid 'cgi/bin
Ah, the caveat of namespace collision -- not actually an issue. The
space is only two-element "$dir/$file" -- otherwise it would not
install in the $PATH. I propose tonail plucking for anyone shipping
*.pm files under a cgi/bin tree.
--Eric
--
You can't whack a chisel without a big wooden mallet.
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
