Re: Slackware 13.0 packaging issue

[Marco Bonetti <marco.bonetti () slackware it>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ok, I've sorted out the issue: it's not a matter of relative links and
it happens both when using my package or the official .run installer.
It's related to the rubygem installation: Slackware does not have gems,
we install it through SlackBuilds.org. The  provided package uses
/etc/profile.d/ to set GEM_PATH in the enviroment: if any of the
framework 1.9.1 gems are installed under system ruby 1.8, they will get
in the way of the msf* executables, breaking things ad causing havoc.
Prepending /opt/metasploit3/lib/ruby/gems/1.9.1 to GEM_PATH and
exporting it in run.sh together with PATH and LD_LIBRARY_PATH make it work.

Is it ok to adopt this solution, or it will break other distributions?

ciao

- --
Marco Bonetti
Slackintosh Linux Project Developer: http://workaround.ch/
Linux-live for powerpc: http://workaround.ch/pub/rsync/mb/linux-live/

My GnuPG key id: 0x0B60BC5F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAksPntYACgkQTYvJ9gtgvF/KWQCfSFPKAqJ/xYUWM6nIzmbhs/r+
h14AoKPrKZZDOXgAn4P/k280pfGHfdcK
=iR5I
-----END PGP SIGNATURE-----
_______________________________________________
https://mail.metasploit.com/mailman/listinfo/framework