From: Anthony Martinez <pi+sup@pihost.us>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] new mail library
Date: Wed, 04 Aug 2010 13:01:40 -0700 [thread overview]
Message-ID: <1280951887-sup-1243@home.mrtheplague.net> (raw)
In-Reply-To: <1280949385.17490.59.camel@raker.ateb.com>
Excerpts from Reid Thompson's message of Wed Aug 04 12:16:25 -0700 2010:
> On Wed, 2010-08-04 at 15:11 -0400, Reid Thompson wrote:
> > On Wed, 2010-08-04 at 14:20 -0400, William Morgan wrote:
> > > Reformatted excerpts from Ben Walton's message of 2010-07-30:
> > > > I just found this (seemingly) awesome new mail handling library. I
> > > > know that rmail has lots of flaws and there has been previously
> > > > expressed sentiment that something better might be nice.
> > >
> > > If it's maintained in the least then it's probaby better than rmail, but
> > > if Sup started require activesupport I would jump off a bridge.
> >
> > not listed in the dependencies.txt
> > http://github.com/mikel/mail/blob/master/Dependencies.txt
>
> but it is listed in the gemspec
> s.add_dependency('activesupport', ">= 2.3.6")
>
Neither of those even resemble a reliable method of checking whether or not the
thing actually uses activesupport. :P
$ pwd
/home/pi/mail
$ egrep -ir require.\*active .
./lib/mail.rb: require 'active_support'
./lib/mail.rb: require 'active_support/core_ext/hash/indifferent_access'
./lib/mail.rb: require 'active_support/core_ext/object/blank'
./lib/mail.rb: require 'active_support/core_ext/string'
There you have it.
--
Several recent languages have adopted an Intercal-like, asynchronous, computed
COME-FROM concept. Only they refer to it with funny terms like "exception
handling". -- Hans Mulder
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2010-08-04 20:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-31 1:47 Ben Walton
2010-08-04 18:20 ` William Morgan
2010-08-04 19:11 ` Reid Thompson
2010-08-04 19:16 ` Reid Thompson
2010-08-04 19:50 ` Ben Walton
2010-08-04 20:01 ` Anthony Martinez [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1280951887-sup-1243@home.mrtheplague.net \
--to=pi+sup@pihost.us \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox