[Tmail-talk] `rake test`, `rake setup` are broken (Was: 6 tests fail using OS X 10.5's apple ruby)
maarten at solovirtuoso.com
Fri Oct 2 03:47:56 EDT 2009
Sorry to hear that maintenance of TMail is on second place now.
However, as a developer of email software I am using TMail, but I'm
not quite happy with it. Due to the legacy code it is difficult to
maintain and extend. RubyMail is a bit cleaner, but it has a low of
flaws. For specific purposes, such as parsing received headers, I
have written my own parser code.
If you plan to develop a completely new gem, think twice about what
you are getting into. It is a daunting task to fully understand the
RFCs, and also be able to parse the mails that are not fully
compliant with RFCs. Did you also think about re-using a proven
existing C/C++ library using FFI, such as VMime or GMime? The
developer of the Nokogiri HTML/XML parser gem choose to use libxml2
under the hood, and his gem is a big hit!
On 2-okt-2009, at 1:45, Mikel Lindsaar wrote:
> On Thu, Oct 1, 2009 at 12:11 PM, Eric Hodel <drbrain at segment7.net>
> eric, sorry for the late reply. The state of the TMail repo has gone
> into a bit of disrepair as I have been focusing on my new mail gem to
> hopefully replace out tmail soonish. But I still want to keep tmail in
> maintain, just not new features as it is getting unwieldy
>> On Sep 30, 2009, at 12:41, Eric Hodel wrote:
>> I started looking into this last test first and determined that
>> there are
>> two scanners, one written in ruby and one in C. (Maybe one of
>> them is out
>> of date and I'm using the out-of-date one?)
> We were thinking about ditching the C scanner in TMail.. lot of work
> for not a lot of gain.
>> Unfortunately it looks like the Rakefile is broken and `rake test`
>> build extensions before starting. From setup.rb:
> Yes... the tool set on TMail is in a bit of a shambles. Someone tried
> to put a whole new toolset in, and it has never really worked 100%,
> but they didn't finish, so... guess that's where it is at.
>> I think, setup.rb should be replaced with Hoe + rake-compiler
>> which are
>> But I can also give you a toolset that will actually work like your
>> contribution page says it should.
> Awesome! Go for it. If you can fork the github repo
> (http://github.com/mikel/tmail/) and patch to your hearts content,
> then we'll release a new gem and then backupload it to rubyforge.
> It's been a long while waiting.
> Rails, RSpec and Life blog....
> Tmail-talk mailing list
> Tmail-talk at rubyforge.org
More information about the Tmail-talk