[sup-talk] unable to sup-sync (new install)

[Magnus Therning]

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