Package Details: sup 1.0-1

Git Clone URL: (read-only, click to copy)
Package Base: sup
Description: Sup is a console-based email client for people with a lot of email. Great mutt alternative.
Upstream URL:
Licenses: GPL
Conflicts: sup-git
Submitter: Garoth
Maintainer: asch
Last Packager: asch
Votes: 52
Popularity: 0.000000
First Submitted: 2009-05-12 15:12
Last Updated: 2020-07-14 09:39

Latest Comments

« First ‹ Previous ... 2 3 4 5 6 7 8 9 10 Next › Last »

Garoth commented on 2011-02-11 19:43

It's very possible to get it working, I was poking the maintainer of ruby-gettext (in community, so it's a little more official) to switch his package to being a gem install. It looks like he's finally done this (though didn't e-mail me about it), so the sup package should be do-able now.

I'm kind of sick/tired at the moment, but I'll hopefully find the energy to throw up the new version soon

Anonymous comment on 2011-02-11 09:14

Are we there yet? Sorry, just can't wait to try it out! Thanks for your work on this!

Garoth commented on 2011-01-27 19:01

Great news everyone. The recent updates to sup and ncursesw as well as discussion with the sup devs has fixed the remaining problems that exist in sup. However, for the moment, the ruby-gettext package in community is somewhat buggy in that it doesn't install as a gem and sup can't find it! I'm asking the maintainer there to change it to a gem style package, but if he doesn't go for that, I'll either make a new package for gettext on aur or find a way to make sup add this non-gem path to its search path for libraries.

Hang tight, I have a running version of sup on Arch with Ruby 1.9. It's coming to you soon!

Garoth commented on 2011-01-25 16:13

--- RuntimeError from thread: main
can't modify frozen string
/usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/account.rb:54:in `force_encoding'

Shit's still really broken. Siiigh. I even tried installing it directly via gem. The gem still depends ncurses, btw -- though it does seem to fall back on ncursesw if it can. Maybe next release / I can bother them on the mailing list.

hollunder commented on 2011-01-24 11:46

0.12.1 is out and supposed to work with ncursesw and ruby 1.9

Garoth commented on 2011-01-17 22:01

Yeah, well, I looked into that ncursesw situation. According to rich lane, they switched back to ncurses because on some weird systems, ncursesw's wide character support caused it not to build because those systems are lobotomized lobsters. Bad reason imo. So ncurses is what we have now.

hollunder commented on 2011-01-17 21:59

I appreciate the work you did so far and I can understand your frustration. If at least the devs were more responsive and would fix their dependency/build mess.. I had really hoped that things would improve with 0.12. It's supposed to use ncursesw now if I'm not mistaken. Well, the build mess and other weird bugs really ruin the experience of a really good idea.

Garoth commented on 2011-01-17 16:23

Sigh. Dunno. I almost got it running, but it throws its own exceptions now -- "can't modify frozen string." This is supposed to be on the bug tracker as bug 128, but the tracker seems to be down, and no replies have been made by mail. Here are some notes on the garbage we gotta do now -- see if you can get it running. I need to do some real work now.

* use ruby-xapian-full
* use ruby-ncursesw even though sup expects ruby-ncurses (which is broken in the gem, and can't be found by sup via aur's fresh build package)
* patch the gem spec to use ncursesw instead of ncurses -- /usr/lib/ruby/gems/1.9.1/specifications/sup-0.12.gemspec (just replace all ncurses with ncursesw manually for the moment)
* need gettext to be a gem and not a regular install... -- pacman -Rd your ruby-gettext and sudo gem install ruby-gettext
* give up and switch to notmuch which is in C. Sad day.

Garoth commented on 2011-01-17 16:08

Sigh, as usual, there are all sorts of problems that I've been trying to work through -- this now seems to require ruby-xapian-full, and can't find ncurses. Looks like the ruby-ncurses pkgbuild doesn't use gem, but sup uses some crazy system that is looking for the gem version of this program. And yet, "gem install" fails with fucking make errors.

What a goddamn pile of shit ruby dependencies are.

Stay tuned.

hollunder commented on 2011-01-15 12:37

0.12 is out and I hope it works with our current ruby version.