>>>>> On Sat, 14 Apr 2007 12:23:48 +0200, Marc Lehmann <[EMAIL PROTECTED]> said:
> On Sat, Apr 14, 2007 at 11:56:23AM +0200, "Andreas J. Koenig" <[EMAIL
PROTECTED]> wrote:
>> The reason for this failure is that Coro per default chooses to not
>> build Coro::Event under a pristine perl and that Continuity has no way
>> to express its wish that it (Coro) be built with event support.
>>
>> Ideally, Marc would ask the user if he wants to build Event support
>> (he asks many questions anyway:) and if the user says yes, then he
>> should put the necessary modules (Event? AnyEnvent? Etc.) into its own
>> prerequisites. The answer should default to yes, so that automated
>> build environments build in doubt too many modules.
>>
>> Would that be OK for you, Marc?
> Hacking around the real problem of CPAN, namely the inability to express
> wishes and preferences, is not really solving anything, the hack will stay
> a hack. (Compare with dpkg for example where packages can recommend and
> suggest in addition to require, or request a specific feature, such as
> AnyEvent).
Of course you're sooooo right, but at this moment now we have a
smaller problem that we might be able to solve, leaving more time for
the larger scale issues.
> The bug seems obviously to be a missing dependency in Continuity: If it
> requires Event, it needs to specify that in its dependencies explicitly,
> as Coro (quite correctly) does not depend on Event at all.
You are shooting too quickly. Continuity *does* specify a dependency
on Coro::Event.
> Current Coro, unlike earlier releases, makes Event *fully* optional,
> as it uses AnyEvent (which suffers most from the inability to specofy
> suggestions or one-of-those-set style dependencies, btw., as it requires
> *one* Event-model module and *prefers* anything over Tk for example).
Coro::Event says the following during Makefile.PL execution (I did
cite this sentence in the previous posting):
Warning: prerequisite AnyEvent 2.51 not found.
Warning: prerequisite Event 1.06 not found.
Warning: prerequisite IO::AIO 2.3 not found.
*** Event not found, not build Event support.
This is a bug in my eyes. It does NOT let the user specify that he
really wants Coro::Event. Except by *installing* something else
beforehand. You are suggesting that this is the way things *should* be
done?
> Forcing Event for no reason seems like a very bad idea - if a package
> relies on Event it should have that dependency, adding it to Coro to help
> those broken packages makes little sense, IMnsHO.
You are so right, but I did not ask you to "Forcing Event for no
reason" but I said:
Ideally, Marc would ask the user if he wants to build Event
I correct myself now, I wanted to say
Ideally, Marc would ask the user if he wants to build Coro::Event
^^^^^^
If my sloppiness has lead you to a wrong impression, I'm sorry.
> The result would only be that Coro would fail to work if Event fails to
> work, even though Coro itself doesn't require that (and a large class of
> Coro users do not require Event either). This seems like a bad tradeoff to
> what seems essentially a workaround for some other module's bug.
If the user has expressed the wish, so be it.
> As such, I would be reluctant to hack around in Coro to add a fake
> dependency that Coro does not really require.
I presume the above correction of my wish sets straight what I'm
really suggesting? I specifically do not ask you to add a fake
dependency that the user does not require. I ask you to do the
opposite: let the user who requires it, build Coro::Event.
> Ideas? Thoughts?
--
andreas
