Skip to content
This repository has been archived by the owner on Mar 26, 2023. It is now read-only.

Install kernel extensions when prims are loaded #328

Merged
merged 1 commit into from Jan 27, 2014
Merged

Conversation

johnnyt
Copy link
Member

@johnnyt johnnyt commented Jan 27, 2014

Closes #327

This is a quick fix.

Next - it will be nice to continue with PR #195

johnnyt added a commit that referenced this pull request Jan 27, 2014
Install kernel extensions when prims are loaded
@johnnyt johnnyt merged commit 75bb360 into master Jan 27, 2014
@Monty
Copy link
Member

Monty commented Jan 27, 2014

The primary reason I didn't default to the changes in RVM that @mpapis proposed in #195 is that we didn't have a way to exhaustively test it on all platform variations and I didn't want to open a potential can of worms.

The simple shell script installer was tested exhaustively and used successfully by people around the world. At least on GS/S and on Maglev 1.8. It seems we frequently had glitches in RVM on some platforms and fixing them without @mpapis was never easy.

Noneltheless, I liked the #195 proposals.

@mpapis
Copy link
Contributor

mpapis commented Jan 27, 2014

@Monty maybe then do a migration, merge the new script and ask users to test it (a bonus point it does not require ruby), but also keep the old script so in case of problems with the new script you can ask users to fallback to the ./install-old.sh/./update-old.sh...

that said - I spent already over a week on rewriting the installation script, it would be a shame to waste that effort ... also I offer my time on fixing maglev installation issues on the new script (as long as someone can support me with topaz/gemstone issues - which is required to finish the new script).

@rjsargent
Copy link

Michal,

We should be able to give you the help you need on Topaz and GemStone
issues. In general, ask on the mailing list. If you cannot get an answer
there, ask me directly and I will relay it to the experts. I cannot
guarantee timeliness in the answers, but we should be able to get you any
help you need.

Thanks,
Richard Sargent
richard.sargent@gemtalksystems.com

On Mon, Jan 27, 2014 at 8:42 AM, Michal Papis notifications@github.comwrote:

@Monty https://github.com/Monty maybe then do a migration, merge the
new script and ask users to test it (a bonus point it does not require
ruby), but also keep the old script so in case of problems with the new
script you can ask users to fallback to the ./install-old.sh/
./update-old.sh...

that said - I spent already over a week on rewriting the installation
script, it would be a shame to waste that effort ... also I offer my time
on fixing maglev installation issues on the new script (as long as
someone can support me with topaz/gemstone issues - which is required to
finish the new script).


Reply to this email directly or view it on GitHubhttps://github.com//pull/328#issuecomment-33386328
.

Richard Sargent
Business Development Manager
503-766-4719
richard.sargent@gemtalksystems.comGemTalk Systems
15220 NW Greenbrier Parkway #240
Beaverton, OR 97006

@Monty
Copy link
Member

Monty commented Jan 27, 2014

As I said, I think using @mpapis scripts would be great. It looks like between @johnnyt and @rjsargeant we could finally make progress. Keeping the old scripts around would allay any of my concerns.

@johnnyt johnnyt deleted the johnnyt-openssl branch January 27, 2014 19:43
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

RVM install is not compiling OpenSSL
4 participants