Re: [Module-build-general] conflicts and test_requires

[Dave R. <au...@ur...>]

On Mon, 3 Feb 2003, Ken Williams wrote:

>
> On Monday, February 3, 2003, at 01:25  PM, Dave Rolsky wrote:
> > There probably needs to be a command line flag to ignore conflicts, or
> > else a module that specifies conflicts could be entirely uninstallable.
>
> What do you mean by "uninstallable"?  The 'conflicts' entries should
> really just generate a warning/error that can be ignored if installing
> by hand, so I'm not sure a special flag is necessary.

Well, I was thinking that something CPANPLUS should respect conflicts but
there'd be a way to override it.  I guess this doesn't need to be in
Module::Build itself.

>
> > Also, was there discussion about a "test_requires" option, so that
> > tests could be skipped if certain modules weren't installed?  Seems
> > like a useful option.
>
> I don't remember such a discussion - I've been thinking of this as the
> primary reason someone might want to put something in the
> "build_requires" field, since typically the actual *building* doesn't
> require any special tools.  But I suppose sometimes it does, like if
> some C library is statically compiled into the module's loadable parts.
>
> Do you think it would be very useful to split test_requires off from
> build_requires?  I'm inclined to leave them as one field, emphasizing
> that testing should usually be a part of the build process.

Well, I was thinking that someone might want to get a "pre-build" module
(whatever that means) and still run the tests.

Also, someone may want to build and install the module but doesn't care if
the tests run.


-dave

/*=======================
House Absolute Consulting
www.houseabsolute.com
=======================*/