From: Tero Tilus <tero@tilus.net>
To: The Sup email client <supmua@googlegroups.com>
Subject: Wiki update proposal
Date: Wed, 11 Nov 2020 12:24:42 -0800 (PST) [thread overview]
Message-ID: <e2f8eac2-2d7d-44e0-8bb6-de6a0777ce08n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1539 bytes --]
Hi,
I have a few tips to add to Debian specific installation page. Apparently
there's no convenient way to submit a PR against GH wiki, so here we go...
diff --git a/Installation:-Debian-and-Ubuntu.md
b/Installation:-Debian-and-Ubuntu.md
index c1136d0..0cb6b7d 100644
--- a/Installation:-Debian-and-Ubuntu.md
+++ b/Installation:-Debian-and-Ubuntu.md
@@ -35,6 +35,11 @@ gem install sup # sudo is not needed if not using system
ruby
```
Note: On a freshly set-up Debian 8.1 with a virgin ruby installation, you
might get an error while trying to install the latest version of Sup, which
is thanks to a missing library (xapian). Easily fixed by fetching the
native Debian version straight from the repository (`apt-get install
ruby-xapian`) and running the above commands again ;)
+If you get `No such file or directory --
/usr/share/rubygems-integration/all/gems/rake-12.3.1/exe/rake`, installing
fresh rake via rubygems (`gem install rake`) might help.
+
+If installation fails on `xapian-ruby` without any specific error message,
try installing that package first (`gem install xapian-ruby`) and then sup.
+
+If you can't or don't want to install gems globally, there's always the
option to install them under your home directory (`~/.gem/`) with `gem
install --user-install <gemname>`. Then you need to also make sure you have
gem binaries in your path. That you can achieve for example by appending
`PATH="$HOME/.gem/ruby/2.5.0/bin:$PATH"` to your `~/.profile`.
### Rubygems `PATH` issue on old systems
--
Tero
[-- Attachment #1.2: Type: text/html, Size: 1802 bytes --]
next reply other threads:[~2020-11-11 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 20:24 Tero Tilus [this message]
2020-11-26 23:01 ` [sup] " Iain Parris
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=e2f8eac2-2d7d-44e0-8bb6-de6a0777ce08n@googlegroups.com \
--to=tero@tilus.net \
--cc=supmua@googlegroups.com \
/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