On Sun, Jan 30, 2005 at 08:22:41PM -0600, Ken Williams wrote:
> > and they do fine.
>
> Not in my opinion. For instance, with Alzabo (at least last time I
> checked) if you have DBD::Pg installed, it'll make you test against a
> postgres database, even if you're not interested in using its Pg
> support.
That's a whole different sort of issue. There's no YAML server that needs
to be installed and configured here.
> >If you want an option that says "don't use Foo::Bar, even if its
> >installed"
> >that's ok.
>
> That's essentially what this is. If YAML is available when M::B is
> installed, then we test YAML support and make a note in the config file
> that it's been tested and is supported. Otherwise we note that YAML
> hasn't been tested and isn't supported.
The trouble is its rather unexpected behavior that this would be set in
stone at install time.
> >But if it was not manually set by the user just try to use
> >Foo::Bar if its available. This DoesWIM.
>
> Again, not in my opinion. Here's a scenario: the user installs M::B,
> without YAML installed, so 'YAML_support' defaults to false. Then for
> some unrelated reason, the user (or a different user on the system)
> installs YAML, and suddenly the contents of META.yml files they
> generate are different, without warning or explanation.
Does it really matter? Shouldn't they be semantically equivalent?
I think you're optimizing for the rather special case of A) a broken
dependent module or B) someone who's really, really picky about their
META.yml layout and in the process breaking the case of the user who
just expects a module to use whatever's installed without being told.
> I do think it's a step forward to make these things explicit and
> configurable by the user. Maybe we need some tweaking of expectations
> or of default behaviors or something, but I do want to keep this
> concept.
I think you're just generating a maintenance nightmare. Again, consider
what it would be like if every module worked this way. If you had to
go through and tweak each individual module's config file to tell it "Yes,
I now have Foo::Bar installed and you should use it."
In the end its not Module::Build's job to test YAML.pm. At some point you
have to trust that your dependencies can take care of themselves else you
wind up trying to test the world.
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
|
