On Fri, 19 Apr 2013 15:18:32 +0200, Jonas Smedegaard wrote:

> > > Recommends: libasync-interrupt-perl | libasync-interrupt-perl, 
> > > libev-perl, libguard-perl
> > 
> > Hm?
> > Did you mean
> >     Recommends: libasync-interrupt-perl | libev-perl, 
> > libasync-interrupt-perl | libguard-perl
> > ?
> 
> Yes, that's exactly what I meant.  Thanks for reading my mind :-D

:)
 
> > Alternatively we could also just add all three to Recommends without 
> > alternatives.
> 
> Only when EV is _not_ available and used is there a benefit of having 
> Async::Interrupt available.
> 
> ...but then again, that means for the cases of explicitly using a 
> different backend it is beneficial to have Async::Interrupt available.
> 
> So yes, I think it is best to plain recommend each of them - even if 
> Async::Interrupt won't actually be _used_ "in most cases".

Ok, makes sense.
Applied in git.

Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Johnny Cash: Give My Love To Rose

Attachment: signature.asc
Description: Digital signature

Reply via email to