Dustin Oprea

@SkyLeach In the case of OSX having such an old version, I'm not sure there's a better way to point to a different version than to just set `LA_LIBRARY_FILEPATH` in...

It was an oversight. Would you be able add a check for LD_LIBRARY_PATH after the existing one? On Dec 15, 2016 6:18 PM, "Matt Gregory" wrote: > @dsoprea I wasn't...

I didn't see any specific reasons why we can't just check for `LD_LIBRARY_PATH` (the conventional variable) in addition to the current variable. This was my original suggestion. Wouldn't the correct...

@SkyLeach Yes. If we're all convinced that this is the way to go, then it'd have to go in [library.py](https://github.com/dsoprea/PyEasyArchive/blob/master/libarchive/library.py).

@SkyLeach See my other inquiry from thirty-five minutes ago.

I need you to walk me through this. As I understand it, there is already a system-global `libarchive` and, if anyone wants a newer one, they'd install it via Brew....

@SkyLeach (and everyone else) I'm suggesting that the affected individuals set the value into `LD_LIBRARY_PATH` using one of the three ways: 1. Prepending the environment change to the command-line that...

Please do. Does this seem like a practical solution for the affected population? On Wed, Feb 8, 2017 at 9:37 AM, Matt Gregory wrote: > Looks good, but I'll need...

It goes back to my original suggestion. `ctypes` doesn't use `LD_LIBRARY_PATH`. I've updated the library-load logic to implement it. Do an update and retry. Note that you can run "./run.py"...

I just went ahead and merged. It's already been tested. Everyone: Please see if this makes it easier for you to cope with running under OS X.