From: magnus@therning.org (Magnus Therning)
Subject: [sup-talk] unable to sup-sync (new install)
Date: Tue, 18 Sep 2007 07:38:52 +0100 [thread overview]
Message-ID: <20070918063852.GB3384@die.therning.org> (raw)
In-Reply-To: <1190048921-sup-8612@south>
On Mon, Sep 17, 2007 at 10:12:15 -0700, William Morgan wrote:
>Excerpts from Kevin Mark's message of Sun Sep 16 20:26:44 -0700 2007:
>> sudo gem install sup -y
>>
>> To run 'sup', I needed to add 'export
>> PATH=/var/lib/gems/1.8/bin:"${PATH}"' to .bashrc
>
>This is a symptom of how Ubuntu deals with gems. Unfortunately there's
>not a lot I can do about it from my end.
There is one thing you _can_ do--make sup easy to package by providing a
setup.rb or install.rb for installation.
Ruby gems and Python eggs seem to suffer from the same problem; they
don't just deal with packaging but also with versioning and they do it
in a way that makes packaging in Linux distros difficult.
See http://pkg-ruby-extras.alioth.debian.org/rubygems.html for Debian's
position on gems.
/M
--
Magnus Therning (OpenPGP: 0xAB4DFBA4)
magnus?therning?org Jabber: magnus?therning?gmail?com
http://therning.org/magnus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20070918/4facb50f/attachment.bin
next prev parent reply other threads:[~2007-09-18 6:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 3:26 Kevin Mark
2007-09-17 17:12 ` William Morgan
2007-09-17 18:07 ` Kevin Mark
2007-09-17 18:59 ` William Morgan
2007-09-18 6:26 ` Kevin Mark
2007-09-18 6:27 ` Magnus Therning
2007-09-18 23:18 ` William Morgan
2007-09-19 1:39 ` Kevin Mark
2007-09-18 6:38 ` Magnus Therning [this message]
2007-09-18 6:54 ` Kevin Mark
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=20070918063852.GB3384@die.therning.org \
--to=magnus@therning.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