So someone on the same server pulled in a gem, that pulled in the latest
minitest.
Suddenly scripts that were running relying on the ruby2.0 builtin minitest
delivered via apt-get failed.
What is the recommended way off forcing a script to "require" the correct
version... even if it isn't "The Latest" and one was delivered via apt-get
and the other via gem?
···
--
John Carter Phone : (64)(3) 358 6639
Tait Electronics Fax : (64)(3) 359 4632
PO Box 1645 Christchurch Email : john.carter@taitradio.com
New Zealand
--
------------------------------
This email, including any attachments, is only for the intended recipient.
It is subject to copyright, is confidential and may be the subject of legal
or other privilege, none of which is waived or lost by reason of this
transmission.
If you are not an intended recipient, you may not use, disseminate,
distribute or reproduce such email, any attachments, or any part thereof.
If you have received a message in error, please notify the sender
immediately and erase all copies of the message and any attachments.
Unfortunately, we cannot warrant that the email has not been altered or
corrupted during transmission nor can we guarantee that any email or any
attachments are free from computer viruses or other conditions which may
damage or interfere with recipient data, hardware or software. The
recipient relies upon its own procedures and assumes all risk of use and of
opening any attachments.
------------------------------
Are you using system ruby or some sort of ruby package manager like rvm?
···
—
Sent from Mailbox
On Wed, Dec 17, 2014 at 2:00 PM, John Carter <john.carter@tait.co.nz> wrote:
So someone on the same server pulled in a gem, that pulled in the latest
minitest.
Suddenly scripts that were running relying on the ruby2.0 builtin minitest
delivered via apt-get failed.
What is the recommended way off forcing a script to "require" the correct
version... even if it isn't "The Latest" and one was delivered via apt-get
and the other via gem?
--
John Carter Phone : (64)(3) 358 6639
Tait Electronics Fax : (64)(3) 359 4632
PO Box 1645 Christchurch Email : john.carter@taitradio.com
New Zealand
--
------------------------------
This email, including any attachments, is only for the intended recipient.
It is subject to copyright, is confidential and may be the subject of legal
or other privilege, none of which is waived or lost by reason of this
transmission.
If you are not an intended recipient, you may not use, disseminate,
distribute or reproduce such email, any attachments, or any part thereof.
If you have received a message in error, please notify the sender
immediately and erase all copies of the message and any attachments.
Unfortunately, we cannot warrant that the email has not been altered or
corrupted during transmission nor can we guarantee that any email or any
attachments are free from computer viruses or other conditions which may
damage or interfere with recipient data, hardware or software. The
recipient relies upon its own procedures and assumes all risk of use and of
opening any attachments.
------------------------------
So someone on the same server pulled in a gem, that pulled in the latest minitest.
Suddenly scripts that were running relying on the ruby2.0 builtin minitest delivered via apt-get failed.
What is the recommended way off forcing a script to "require" the correct version... even if it isn't "The Latest" and one was delivered via apt-get and the other via gem?
I think that the most popular way is using bundler: bundler http://bundler.io
--
John Carter Phone : (64)(3) 358 6639
Tait Electronics Fax : (64)(3) 359 4632
New Zealand
This email, including any attachments, is only for the intended recipient. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission.
If you are not an intended recipient, you may not use, disseminate, distribute or reproduce such email, any attachments, or any part thereof. If you have received a message in error, please notify the sender immediately and erase all copies of the message and any attachments.
Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission nor can we guarantee that any email or any attachments are free from computer viruses or other conditions which may damage or interfere with recipient data, hardware or software. The recipient relies upon its own procedures and assumes all risk of use and of opening any attachments.
"As you set out for Ithaca, hope the voyage is a long one, full of adventure, full of discovery [...]" - C. P. Cavafy
···
On 17 Dec 2014, at 23:56, John Carter <john.carter@tait.co.nz> wrote:
PO Box 1645 Christchurch Email : john.carter@taitradio.com <mailto:john.carter@taitradio.com>
On Wed, Dec 17, 2014 at 2:03 PM, Raj Sahae <rajsahae@gmail.com> wrote:
Are you using system ruby or some sort of ruby package manager like rvm?
—
Sent from Mailbox
On Wed, Dec 17, 2014 at 2:00 PM, John Carter <john.carter@tait.co.nz> > wrote:
So someone on the same server pulled in a gem, that pulled in the latest
minitest.
Suddenly scripts that were running relying on the ruby2.0 builtin minitest
delivered via apt-get failed.
What is the recommended way off forcing a script to "require" the correct
version... even if it isn't "The Latest" and one was delivered via apt-get
and the other via gem?
--
John Carter Phone : (64)(3) 358 6639
Tait Electronics Fax : (64)(3) 359 4632
PO Box 1645 Christchurch Email : john.carter@taitradio.com
New Zealand
--
------------------------------
This email, including any attachments, is only for the intended recipient.
It is subject to copyright, is confidential and may be the subject of legal
or other privilege, none of which is waived or lost by reason of this
transmission.
If you are not an intended recipient, you may not use, disseminate,
distribute or reproduce such email, any attachments, or any part thereof.
If you have received a message in error, please notify the sender
immediately and erase all copies of the message and any attachments.
Unfortunately, we cannot warrant that the email has not been altered or
corrupted during transmission nor can we guarantee that any email or any
attachments are free from computer viruses or other conditions which may
damage or interfere with recipient data, hardware or software. The
recipient relies upon its own procedures and assumes all risk of use and of
opening any attachments.
------------------------------