[Citadel Development] (no subject)

2011-12-22 Thread IGnatius T Foobar
>ares_parse_mx_reply is the reason why we need a recent version; it >was added about a year ago by the node.js guys. Ok, that worked really well. Now we can check for the right version. Is there a similar function we can check for in libev? If so, then we can look for that instead

[Citadel Development] Re: Net::Citadel in Debian

2011-12-22 Thread dothebart
Thu Dec 22 2011 15:04:07 EST from jame @ Rocasa Mail System Subject: Re: Net::Citadel in Debian  I'm not sure if new packages are automatically picked up by Ubuntu but I'll follow up about that later. yes, they do, but on irregular basis... which is the reason why they have some pretty awkwa

[Citadel Development] Re: Net::Citadel in Debian

2011-12-22 Thread jame
  Sun Dec 11 2011 12:30:28 PM EST from jame Subject: Net::Citadel in Debian FYI, The v0.02 Net::Citadel Perl module has been accepted into Debian unstable as the package libnet-citadel-perl. And has now migrated to Debian Testing, so there shouldn't be any issue with it being available

[Citadel Development] (no subject)

2011-12-22 Thread dothebart
Thu Dec 22 2011 08:09:27 EST from IGnatius T Foobar @ Uncensored I added a configure check for libev version. I couldn't figure out how to do it for c-ares though. Is there perhaps an API call that is only available in the new version that we can check for? ares_parse_mx_reply is the reason

[Citadel Development] (no subject)

2011-12-22 Thread IGnatius T Foobar
I added a configure check for libev version. I couldn't figure out how to do it for c-ares though. Is there perhaps an API call that is only available in the new version that we can check for?