Managing different versions of libraries/modules

Discussion in 'Ruby' started by H. Simpson, Jul 30, 2004.

  1. H. Simpson

    H. Simpson Guest

    Does Ruby suffer from the same problems as "dll hell"?

    How does Ruby 1.8.2 handle different versions of 3rd party ruby modules
    being required by different scripts?

    Do 3rd party ruby module names need to include version numbers when they
    become incompatible with prior versions?
     
    H. Simpson, Jul 30, 2004
    #1
    1. Advertising

  2. On Sat, 31 Jul 2004 03:31:42 +0900, H. Simpson
    <> wrote:
    > Does Ruby suffer from the same problems as "dll hell"?
    >
    > How does Ruby 1.8.2 handle different versions of 3rd party ruby modules
    > being required by different scripts?
    >
    > Do 3rd party ruby module names need to include version numbers when they
    > become incompatible with prior versions?


    Ruby does not yet have a built-in solution for library versioning
    issues. There are a couple of third-party approaches that may
    ultimately find their way into Ruby at the core, but they are not
    feature complete and matz has not indicated one way or another except
    that they must meet the usual level of quality.

    -austin
    --
    Austin Ziegler *
    * Alternate:
     
    Austin Ziegler, Jul 30, 2004
    #2
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Replies:
    1
    Views:
    311
    Victor Bazarov
    Dec 7, 2006
  2. Daniel Pitts
    Replies:
    0
    Views:
    328
    Daniel Pitts
    Nov 14, 2007
  3. ks
    Replies:
    9
    Views:
    421
    Jorgen Grahn
    Mar 20, 2010
  4. Ken Bloom
    Replies:
    2
    Views:
    134
    Ken Bloom
    Nov 4, 2008
  5. Nzyme11
    Replies:
    0
    Views:
    71
    Nzyme11
    Jun 4, 2014
Loading...

Share This Page