The USPTO Registered Logo Badge of the Medical Marijuana Initiative of North America - International Limited, an Arizona Benefit Corporation to the left of Mt Hood sunlit from the northwest in June followed by the proprietary MMINAIL octocopter delivery bot.

Ruby Macports

Welcome! This is the Ruby Macports page of the MMINAIL.

Note. This page has explicit access to the local jQuery library as well as to a local complimentary working (.js) file.

More to come ...

Ruby Macports 2nd Instance

So, ya wanna upgrade Ur system Ruby AND learn a little Homebrew, heh?

Via Jekyl, no doubt.

This is a very sensitive area of juxposition for the Internet, the Coding Community, and for Global Intelligence in general.

Cuidado! You must tread lightly, and carry a big Unix stick! ~ Steve Jobs"

Especially when working with your 'fixed-in-concrete' system Ruby and the dreaded entrenched Macports.

Binary Archives (.tbz2)

Macports pre-compiles Port(s) into Binary Archives (BA), or Port files called MacPort BA(s) and then stores the finished products on a remote server.

The finished MacPort BA(s) are then tagged eligible for download via Macports dot org.

In addition, MacPort BA(s) in (.tbz2) format are also created both locally and automatically in the /opt/local/var/macports/software/ subdirectory of your Macports initial ( default ) install or in your Macports 2nd ( Macports241 ) install whenever port installs a Port file.

Caveat. The MacPort BA(s) can only be used on a target system running Macports.

For example, a MacPort BA cannot be installed on a system that relies solely upon Homebrew, or the Fink Project.

Build Phase

The build phase of an install is usually the phase that takes the longest amount of time to run in terms of milliseconds.

Macports allows a MacPort BA and an accompanying set of utilities to skip the build phase of an install and to begin installation of an application right after the 'destroot' phase.

As a result, applications need not be compiled when installing to on a target system capable of handling MacPort BA(s).

For this capability, the administrator must download and install Macports onto the development machine.

Destroot Phase

More to come ...

Binary Packages (.pkg)

Binary Packages, or BP are stand-alone Binary installers that are pre-compiled.

And, as such ... do NOT require an accompanying set of Macports utilities.

Separate Install of Macports

A 2nd install of Macports on your development machine will give you the capability of locally creating BP ... For distribution (if licensed).

And, thereby avoiding conflicts with Port files on systems that already have an initial default copy of Macports installed.

In addition, a utility exists via Macports should you wish to distribute your software via (.dmg) rather than (.pkg) formats.


To perform a 2nd install of Macports on your development machine that is separate from the initial default /opt/local/ install, focus on the following two (2) command switches.

Create a second App trigger ...
In the Applications folder.


Create an Alt directory ...
To Install Into.

Note. The --prefix switch accommodates the alternative directory.

Whereas, the --with-applications-dir switch avoids conflict with your already existing local Applications/MacPorts folder.

Rule. Stay with the opt directory of your machine root, and build a 2nd install of Macports in an alternative subdirectory.

For example, /opt/Macports241/.

The Issue

Why fuss with another instance of Macports?

Analysis. When the issue of solving why your local Jekyll server hangs when given the previous accurate start command of ...

Jekyll Start Command ...
jekyll serve --watch --baseurl ""
Was working fine!

Prior to the attempted upgrade to Ruby 2.4.0 via Homebrew ...

Conclusion. The "fuss" Becomes paramount to further development.

Download and Unpack

Navigate via the Finder to the location of your preferred and separate 2nd install of Macports ie.) /opt/Macports241/.

When you have arrived at your destination, right-click over the subdirectory name in order to expose the Services tab.

Now, select a 'new Terminal window at folder' to open up the Terminal program.

Before the administrative instant User can unpack a Port file ... ( In this case Macports base ver 2.4.1 ), the BA must be downloaded.

The following code must be executed in the Terminal in order to download the requested Port file from Macports, as follows:

Download Macports base ver 2.4.1
curl -O

Next, unpack the BA file with the following Terminal command ...

Unpack n Un-b-zip! ...
tar xf MacPorts-2.4.1.tar.bz2
Pronto! Andele!

This places an exploded subdirectory of name same ie.) MacPorts-2.4.1 in the /opt/Macports241/ folder.

    Whoosh! ( Interlude )


Before we can start building a 2nd instance of Macports on your local development machine ...

We must perform something that appears to be counter-intuitive, but once achieved illuminates the pathway to the success of all of your many hours (and, days?) of learning, expanding, and troubleshooting.

¡Recuerde!. In order to pull this off, we must depart from our standard working User and become an administrative instant User ... on the same machine!

Binary Path(s)

The binary path(s) of the initial install /opt/local/bin:/opt/local/sbin: must be commented out from the instant User $PATH variable.

Why? Because the locations the export statements represent must not be present during the Build of the 2nd instance of Macports.

Destination Known

Once we make it to a successful install of a 2nd instance of Macports, we can then upgrade both Ruby to version 2.4.0 and Rubygems to 2.6.11 via another separate Build of a BA, and a call via upgraded gem.

Rather than attempting to install another copy of Ruby through Macports ( this is what hung the local Jekyll server in the first place! )

Or, through Homebrew ( does Homebrew even have their Ruby-24 BA back on the bottle rack again? )

Or, through RVM ... Who was, by the way, feeding off of the error codes generated by Homebrew!

A conspiracy to rig the market in favor of Homebrew? Naw, the RVM boys were just being cautious. Short of allowing the install, the RVM bots were quite accommodative.

Fight Fear w More Fear?

Ya know ... Macports has already countered with a scare claim of their own against the /usr/local/ subdirectory at their online documentation site.

( As opposed to the Macports preferred subdirectory of choice ... /opt/local/ ).

Yep! Created a whole sub-section at their menu of directions to house the scare claim against /usr/local/.

What? Are you all Trump voters? Or, something? Out there in coding land?

Back In Black

Back to the Binary Paths! We've got more work to do there!

Simply right-click over the hidden dot bash underscore profile file located in the root directory of the instant administrative User ... And, open the file for editing in TextEdit.

Once open, simply prepend the export statement that contains a reference to the above Macports binary path(s) with a keyboard 'hash' symbol, or #.

Note. The export statement was originally placed in the dot bash underscore profile file at the time of the initial install of Macports.

After placing the 'hash' symbol, or # appropriately at the front of the export statement ... ( in order to comment the export statement out ), save and close TextEdit.

Now that the instant administrative User's dot bash underscore profile file has been corrected, we must now rebuild the $PATH variable.

Rebuilding The $PATH Variable

First, after editing the the hidden dot bash underscore profile file ... The Terminal program must be 'rebooted'.

  • Close the Terminal Window,
  • Close the Terminal Program,
  • Re-open the Terminal Program.

The path_helper Command

To perform a rebuild of the $PATH variable, at the Terminal prompt enter the 'path_helper' command, as follows:

The path_helper Command ...
Use the full path to the command.

A subsequent echo of the $PATH variable should now reveal an absence of any 'opt' type subdirectories in the administrative instant User path.

Look for opt(s) ...
echo $PATH
No opt(s) allowed!

Configure Time

Be sure you have navigated via the Finder to the location of your unpacked tbz2 copy of Macports ver 2.4.1.

Now right-click over the accepted subdirectory to open up the Services tab, a new Terminal window at folder.

Have Macports set the directory of your --prefix switch to the target destination of your 2nd instance with the following Terminal statement.

The Target Destnation
Configure, Make, Install

Have Macports set your machine's Applications folder to receive a separate, 2nd Macports install folder named 'Macports241'.

Note. Because this command statement will also start the configuration process of the 2nd instance ... You will need to perform this step as a super-user.

Please have your administrative instant User password ready.

Compiling The Code ...
sudo ./configure --prefix=$MP_PREFIX  ➡️  
Follow along w the machine ...

A verbose, line-by-line and blow-by-blow compilation will be printing to the Terminal window.

For example, here is an unusual looking line from the compile timeline ...

GNU Step Foundation Library
is not defined in your environment, ➡️
preventing the use of ➡️
GNUstep's Foundation library
Sub Apple Foundation Library

Until you realize the GNU Foundation Library closely resembles Apple's Cocoa (formerly NeXT's OpenStep) API.

And, now you see the compilation process opted for the Mac OSX Sierra Xcode Command Line Tools ver 8.3 default to the Apple Foundation Library.

Make It Happen

Next, we must 'make' the now compiled 2nd instance by simply typing the command make at the Terminal window as a super user.

Only super-users make ...
sudo make
Be a super-user!

Note. There were (50) warnings during the make with basically the same message.

RE: SysCall deprecated ... Please use a supported interface

For more information, including the Terminal report of the make section in question ... See the private GIST located at GitHub.

Time To Install

Ok, it's time to install what we've made with the following command statement.

From the Terminal,

Install the Make
sudo make install
Local admin su doer

Finally, after a successful build, add the location to the 2nd instance bin ie.) /opt/Macports241/bin to your administrative instant User dot $PATH variable by opening the bash underscore profile file once again.

Include the following export statement in the file ...

Add a new line
export PATH="/opt/Macports241/bin:$PATH"
Save and close

Keep the original two binary paths from the initial install of Macports commented out by the keyboard 'hash' symbol, or #.

Now that we have changed the administrative instant User dot bash underscore profile file for a second time ...

Once again, we must reboot the terminal for the changes to take effect.

  • Close the Terminal Window,
  • Close the Terminal Program,
  • Re-open the Terminal Program.

Rebuild The $PATH

Recall to perform a rebuild of the $PATH variable ...

Remember to enter the following line of code at the Terminal prompt.

Enter the path_helper command, as follows.

Use every time after an edit
To rebuild the $PATH variable

Similar to before ...

A subsequent echo of the $PATH variable should now reveal the inclusion of a single 'opt' type subdirectory ie.) /opt/Macports241/bin in the administrative instant User path.

Congratulations! You have successfully installed a 2nd instance of the MacPorts system!

To get the accompanyng Port file(s), if any ... And, to update the system, run the following line of code ...

Ensure Macports is fully functional
sudo port -v selfupdate
Under this instance.


MacPorts base is already the latest version ...

The ports tree has been updated.

To ensure all installed Port files have been upgraded to the Macports max ...

Run the following command from the Terminal prompt as a super-user, as follows:

Upgrade all Port files.
sudo port upgrade outdated
aka Binary Archives


Nothing to upgrade.

Further Review

For further review,

Please read 'man port', the MacPorts guide.

Also, please read the Macports Wiki.


Supporting Content

Welcome! This is the Supporting Content section for the MMINAIL Central Live Repository.

E Books

With today's explosion of modern devices, some consumers like to read their articles on their Kindles or iPads.

Therefore, a method to convert any page of this website into an 'eBook' is auto-built into the top of the navigation stack as well as in the footer of every page.

Simply click the small dot epub button eBook icon to render the current page as an Overdrive (.epub) or a Kindle (.mobi) for external reading.

Note. The Apple iBooks platform also reads and displays the (.epub) format.

The A's Have It!

In today's complicated world of coding, even the use of the standard hyperlink has come into question.

Therefore, to make it easy for the end-user, this User Interface, or UI will show safe internal links in the bootstrap default color of light dodger blue.

On the other hand, external links, when designated https secure ... Will be shown in the color of forest green.

All other external links designated with standard http will be shown in the color of indian red.


For an acronym to be visually effective when reading a line of text, the acronym must first be declared.

In addition, the acronym must stand out from the body of information.

To accomplish both of these objectives, the authors have selected Ashley Gold, a primary color within the registered logo badge of the Benefit corporation for which to highlight acronyms.

Whenever the end user spies a designated acronym of Ashley Gold color, simply hover over the acronym to reveal the underlying meaning of the acronym letters.

Screen Responsiveness

This page has been tested for mobile responsiveness on a virtual Galaxy S5 smartphone emulator.

The authors have determined the accuracies of the page renderings at both a portrait width of 360px and a landscape width of 640px.

In addition, pages are also tested against an Amazon Kindle Fire HDX 7, 3rd Generation tablet.

On the Kindle tablet, both portrait and landscape renderings appear accurate, as well.

And, on the Amazon Fire phone, using automatic screen rotation, both portrait and landscape renderings appear accurate.

How To Navigate This Website

  • The Navigation to your right is set up to return to this Home page by clicking on the Home icon   south of the divider.

  • To select any of the other topics or subtopics, simply click on the corresponding glyphicon to open up the referenced file.

  • If you get stuck, simply click on the Home icon   below the divider to be hyperlinked back to this Home page.

Got An Idea?

If you have an idea that will spruce this site up even better than it already is, then you know the drill.

Simply go ahead and fork this repo, make your changes, and send me a pull request.

Site Monitoring

Note. The Http Headers of this repo are being monitored by Internet Supervision dot com

25 Mile Rule

The MMINAIL is dedicated to the preservation of the hard-earned rights of Medical patients to grow up to (12) state-legal Medicinal plants.

In a connective cartography of ideas and hyperlinks spanning the entire connectome of the modern Medical Marijuana Initiative ...

The open source authors of this project hope to enlighten the world to the plight of the common medical patient.

Due to a labyrinth of government regulations and costs, today's common medical patient is virtually devoid of healing phyto-cannabinoids and other beneficial terpenes globally for no other reason than his or her current residential address.


"When residing 25 miles extant of a state legalized dispensary"

Doesn't that sound a bit strange to you?

Restricting access to medicine ...

Almost Un-constitutional, isn't it?

And, with patients in Arizona paying anywhere from $75 to $90 USD for a (1/8) ounce of medicine ...

Don't you think it is time that we allow ALL patients the right to grow, stash, and cure their own medicines?

Make Contact

We do at the MMINAIL.

If you agree, why don't you donate a little spare cash?

Or, a little of your coding time?

Or, simply contact your favorite Arizona State Senators and Congressional Representatives today!

No Warranty

Disclaimer. The author of this website has made every effort to ensure the accuracy of the information herein.

However, the information contained in this website, and in its pages, is offered to the public without any warranty expressed or implied.

Therefore, the author of this website, and by extension its pages and content cannot be held liable for any damages that may be caused indirectly or directly by the software instructions or tutorials contained in the pages of this website.

For further review, please see the License page of this website and/or the Privacy Policy page of this website to clarify.

Reproduction In Part

Most authors will allow the reproduction of their works in part when the case of brief quotations embodied in critical articles or reviews is addressed.

Therefore, please remember to provide a Link-back to the original author, or to the publisher of the original publication when citing.

Thank you for your consideration.

Fork It

If you are an expert in your field of specialty, then I suggest you fork the working repo of this Website and create a Sub-menu topic of your choosing that may be beneficial to our readers.

Send us a Pull Request.

Our team of coders will review your contribution and get back to you with a "thumbs up" ( or, "thumbs down" ).

Can You Contribute Code?

As we can now decipher the time spent by our functions at the code block level ...

How much of your coding time are you willing to invest in this project?

As we rely heavily upon contributions from the coding community, your contribution of code will be greatly appreciated.

Can You Contribute Cash?

As we can now spend the equivalent of our grandparents' monthly mortgage payment at our local Sunday football games ...

How much of your spare cash are you willing to invest in this project?

As we rely heavily upon contributions from the coding community, your contribution of cash will be greatly appreciated.

Can You Contribute Ether?

As we have witnessed the growth of Bitcoin (BTC) from 8 cents to $10,000 USD over the course of the last decade ...

How much of your spare Ether ( ETH ) are you willing to invest in this project?

As we rely heavily upon contributions from the coding community, your contribution of ether will be greatly appreciated.

Public Hash

Scan the following QR Code to extract the Public hash in support of our Medcoin™ Crypto Currency Project.

QR Code - Click to Reveal - the Medcoin Public Hash

Thank you for your contribution.

The Management

The USPTO Registered Logo Badge of the Medical Marijuana Initiative of North America - International Limited, an Arizona Benefit Corporation

Copyright © 2000 - 2017

The Medical Marijuana Initiative of North America Small Registered MMINAIL™ Logo Badge Small Registered MMINAIL™ Logo Badge
- International Limited Small R-Reggae™ Trademark Symbol Logo Badge Small R-Reggae™ Trademark Symbol Logo Badge