#6850 Use /usr/bin/env python for ipaclient via pypi / macOS fixes for ipaclient
Closed: fixed Opened by neffs.

I just installed ipaclient on macOS, which seems to work fine after two patches:

libkrb5 uses another name: https://github.com/freeipa/freeipa/pull/699

/usr/local/bin/ipa uses #!/usr/bin/python which is the system provided python version on macOS. I use python from homebrew (https://brew.sh) which is installed in /usr/local/bin

I think it would be best to use a fixed path for RPM packages but if you install using pip env should be used.
I'm not sure how /usr/bin/python ends up in the whl file, so I couldn't include it in the pull request.


Ticket #6653 should address and fix any path issues.

Metadata Update from @cheimes:
- Issue assigned to cheimes

After checking again on a fresh system, I remembered that some more work is needed....

If someone else wants to use ipaclient on macOS:

install homebrew (https://brew.sh)
brew install python nss

Get python-nss from pypi and install it manually:
export LDFLAGS=-L/usr/local/opt/nss/lib
python setup.py install --include-root=/usr/local/opt/nss/include --include-root/usr/local/include

pip install ipaclient

I got good news for you. FreeIPA 4.6 client will no longer depend on python-nss.

PR https://github.com/freeipa/freeipa/pull/700 turns ipa CLI into a proper entry point.

Metadata Update from @mbasti:
- Issue set to the milestone: FreeIPA 4.5.1

master:

  • bf67974459f093487a1c5a49234769803780ecbe Use entry_points for ipa CLI

ipa-4-5:

  • 1e1e4e8ef2d2486068e17228c8a0f8b1a2b099f5 Use entry_points for ipa CLI

Metadata Update from @mbasti:
- Issue status updated to: Closed (was: Open)

Metadata Update from @mbasti:
- Issue close_status updated to: fixed

Metadata