# from Michael G Schwern
# on Tuesday 20 November 2007 17:24:
>Eric Wilhelm wrote:
>> I know it sounds like a hack, but perhaps the complete solution *is*
>> to use perl "modules" for identifying all applications.
>> ...
>> I think we would maybe benefit from making the 'external::'
>> namespace special.
>Syntax-wise, I'd rather see something like this:
>
> requires:
> external:
> svn: 1.4.2
> mysql: 5.0
> python: 2.1
>
>That way there is no ambiguity about whether a given requires key is a
> module name or something special. Module names have simple values,
> special keys have complex values. Then there is no name clash.
Well, using the standard namespace and shipping 'external/svn.pm' means
the installers don't need an upgrade. (The double-edged sword of
ad-hoc.)
The scheme as-described implies the need for an external.pm and some
sort of API (plus possibly a plugin architecture or registration
mechanism.)
--Eric
--
"But as to modern architecture, let us drop it and let us take
modernistic out and shoot it at sunrise."
--F.L. Wright
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
