@sstephenson it's not up to an implementation to support or not support an installer. The reverse is true.
@brixen @sstephenson could that relationship be reversed? Could impls ship their own "recipes"?
-
-
@bascule@sstephenson I have repeatedly asked RVM to just coordinate what Rubinius provides. That is how the tool should be written. -
@brixen@sstephenson doesn't seem like that approach is working very well ;) -
@bascule@sstephenson which approach? -
@brixen@sstephenson if the impl-specifics were abstracted away, installers wouldn't have any choice but to do it your way
End of conversation
New conversation -
-
-
@bascule@MagLev does via install/update scripts but RVM hijacked/rewrote them for logging. /c@brixen@sstephenson -
@jc00ke@MagLev@brixen@sstephenson I'm thinking of a common recipe framework (shell, rb, or otherwise) all impls could share -
@bascule@jc00ke@MagLev@brixen@sstephenson +1 installation should be decoupled, so all switchers can make use of, and for provisioning.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.