From: Hamish <dmishd@gmail.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: [sup-devel] mail gem no longer needs activesupport [was: sup-server revisited]
Date: Sun, 08 May 2011 17:36:22 +0100 [thread overview]
Message-ID: <1304872142-sup-6096@whisper> (raw)
Excerpts from William Morgan's message of Tue Feb 22 21:29:07 +0000 2011:
> Reformatted excerpts from Tero Tilus's message of 2011-02-22:
> > Would it be time to go for https://github.com/mikel/mail now? It would be
> > supported and actively developed and I really like the API. As a
> > downside, depending on activesupport pulls in a whole a lot of fluff and
> > using treetop may suggest that parsing might hog a little more cpu and
> > memory than is absolutely necessary.
>
> I looked at it, but the dependency on activesupport is a dealbreaker for me.
> There's no way I would pull that pile of Rails shit into Sup.
Might be a bit late, but I've just noticed that they're taking the
activesupport dependency out, as of mail 2.3.0
http://rubygems.org/gems/mail/versions/2.3.0 - no activesupport
On github, the gemspec no longer refers to it:
https://github.com/mikel/mail/blob/master/mail.gemspec
though the Gemfile still does ... I think this is an oversight.
https://github.com/mikel/mail/blob/master/Gemfile
A couple of commits doing the work:
https://github.com/mikel/mail/commit/6eb4c44a15eb1707dde60959e85e5c536ef136e2
https://github.com/mikel/mail/commit/8bea8ede624e81fb4704e66097a1c8cf35f8de8d
> RMail is not great and I don't like using it, but it really is the best
> thing I've found so far. I think I have whipped it into shape pretty well in
> heliotrope.
>
> > Who would give us bindings to GMime and wrap it inside Mail API...
>
> I would use GMime bindings in a heartbeat.
Hamish
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2011-05-08 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 16:36 Hamish [this message]
2011-05-10 12:06 ` William Morgan
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=1304872142-sup-6096@whisper \
--to=dmishd@gmail.com \
--cc=sup-devel@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