Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: carmen <_@whats-your.name>
To: sup-talk@rubyforge.org
Subject: Re: [sup-talk] Arch Linux sup now failing.
Date: Fri, 3 Sep 2010 23:01:55 +0000	[thread overview]
Message-ID: <20100903230155.GA4001@myhost.Belkin> (raw)
In-Reply-To: <1438.143.205.216.185.1283536658.squirrel@lavabit.com>

> How can a stupid minor version change break things so badly?
Arch totally hosed 1.9.2 here too. way beyond sup, into justnuking Gem-installed lib functionality in general

actually, ive never used sup beacuse it refuses to find my mail (notmuch has no issues) because its not in {cur,new,tmp} subdirs. nor does it seem to recursively dig. but i spent a while and there was just too much code to read, so i wrote my own webmail [ http://gitorious.org/element/element/blobs/master/ruby/W/mail.rb ] 

well, TMail is totally broken on 1.9.2, and RMail (as sup uses) and Mail (from TMail's maintainer and now abandoner) is simply way too slow as theyre pure-ruby

unless you install activeSupport 2.3.x which has a hacked tmail that runson 1.9.x

anyways.. i'm trying to figure out a good permanent solution to this, and it seems to involve rewriting eveyrthing in HAskell..
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  parent reply	other threads:[~2010-09-03 23:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-03 13:13 Daren Lord
2010-09-03 13:33 ` Piotr Kempa
2010-09-03 17:57   ` hollunder
2010-09-03 18:13     ` Gaute Hope
2010-09-03 18:25       ` Gaute Hope
2010-09-03 23:01     ` carmen [this message]
2010-09-04  9:05       ` Philipp Überbacher
2010-09-03 15:26 ` Arian Kuschki

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=20100903230155.GA4001@myhost.Belkin \
    --to=_@whats-your.name \
    --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