Mac OS X support

[overlookmotel]

Hello.

PR #1 concerning Mac OS X support has been quiet for a couple of years.

Can I ask: is digital_cinema_tools_distribution supported on OS X currently? In my particular case, I'm on OS X 10.9.5 Mavericks.

[overlookmotel]

When running the setup script on my OS X laptop, I get the message:

This installer supports only linux systems

[overlookmotel]

Hello. Just wanted to give nudge on this. Are there any plans to support OS X? Or anything I can do to help make it compatible? I'm very keen to start using dcp_inspect on Mac machines for a film festival starting in about a month...

[kieranjol]

Any update on this? I'm mostly interested in running hash checks, so it would be great if this could run on OSX.

[overlookmotel]

@kieranjol Someone has posted a method to install dcp_inspect on Yosemite: wolfgangw/backports#53 (comment)

But I haven't tried it. Please let me know if it works for you.

[overlookmotel]

@kieranjol I've been using dcp_inspect on my Mac by running it inside a Virtualbox virtual machine running Ubuntu, which does work, but it's a bit of a pain to set it up.

[overlookmotel]

@kieranjol Just to let you know, I can confirm that @pm974's instructions in wolfgangw/backports#53 (comment) worked for me to install on OS X Yosemite 10.10.5 with asdcplib 2.5.12.

[wolfgangw]

@overlookmotel @kieranjol macOS support is back on the table. Would be great if you could test. See https://github.com/wolfgangw/digital_cinema_tools_distribution/wiki/Setup

[overlookmotel]

Have not been able to test install script yet. Problem is I don't have a Mac which doesn't already have dcp_inspect installed by some other hacky methods, and not running the install script "clean" wouldn't be a useful test of whether it works properly.

In meantime, one question about the install instructions. They say:

When finished run exec /bin/bash and you're done.

Does that mean that you have to run exec /bin/bash

1. Before the install script curl -sLO ...? or
2. After the install script? or
3. Before running dcp_inspect each time you inspect a DCP?

If the latter, that's not ideal. I am able to run dcp_inspect with zsh with my hand-made install (though I always disable audio analysis with --na, so maybe that's the part that requires bash?)

[wolfgangw]

I tested clean runs with pristine accounts:

• add a user, make him admin (required for brew installation)
• login as that new user
• install brew (this will change ownership of an existing brew installation - fix later for your primary account with what brew doctor tells you to do, it'll be alright again)
• run curl -sLO https://git.io/digital-cinema-tools-setup && bash digital-cinema-tools-setup
• run dcp_inspect (btw, the audio analysis hang on macOS is fixed)

Bit of a hassle because of the required brew doctoring but it is a useful test.

Wrt the bash thing: yes, bash not at all required to run dcp_inspect in principle.

It's just that I remembered late (with the 'clean' runs) that bash is not the default shell on macOS (first thing I had changed on this new box was default shell). digital-cinema-tools-setup writes required PATHand rbenv/ruby-related stuff to .bashrc - assuming everyone is using bash -_-.

Stuff could just as well go to .zshrc, I reckon.

So, as of today, and merely as a workaround for the time being, you indeed need to be in bash to run the right ruby with the required gems and have your PATH set up right - which exec /bin/bash will do.

Yes, let's fix that.