Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make compatible with macOS #29

Closed
reitzig opened this issue Jul 30, 2019 · 4 comments
Closed

Make compatible with macOS #29

reitzig opened this issue Jul 30, 2019 · 4 comments
Assignees
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@reitzig
Copy link
Owner

reitzig commented Jul 30, 2019

Due to differences in default programs, sdkman-for-fish currently doesn't work on macOS. Issues include

  • non-GNU stat (see also this comment),
  • sha256sum unavailable (test only).

We'll need tests and then see what we can do about whatever pops up.

@reitzig reitzig added enhancement New feature or request help wanted Extra attention is needed labels Jul 30, 2019
reitzig added a commit that referenced this issue Jul 30, 2019
And mercy be with us all.

 - Use `apt` and `homebrew` addons for simplicity and build speed (?).
 - Make build matrix explicit: can't handle installing different
   versions of fish otherwise.
reitzig added a commit that referenced this issue Jul 30, 2019
And mercy be with us all.

 - Use `apt` and `homebrew` addons for simplicity and build speed (?).
 - Make build matrix explicit: can't handle installing different
   versions of fish otherwise.
reitzig added a commit that referenced this issue Jul 30, 2019
And mercy be with us all.

 - Use `apt` and `homebrew` addons for simplicity and build speed (?).
 - Make build matrix explicit: can't handle installing different
   versions of fish otherwise.
@reitzig
Copy link
Owner Author

reitzig commented Jul 30, 2019

While the fish 2.7.1 formula exists, curl as called by Travis doesn't find it; Homebrew became homebrew. D'oh? This fails the test with fish 2 right at the start.

@reitzig
Copy link
Owner Author

reitzig commented Aug 1, 2019

In test/completions.rb, we're getting:

find: -printf: unknown primary or operator

There's another red test:

  Testing 'sdk use ant 1.9.9 > /dev/null; sdk broadcast'
  - sout ok!
  - status ok!
  - path bad:
    7a8
    > /Users/travis/.sdkman/candidates/ant/current/bin
  - anthome bad:
    1c1
    < /Users/travis/.sdkman/candidates/ant/1.9.9
    ---
    > /Users/travis/.sdkman/candidates/ant/current

@reitzig
Copy link
Owner Author

reitzig commented Nov 5, 2019

One test remains red:

  Testing 'sdk use ant 1.9.9 > /dev/null; sdk broadcast'
  - sout ok!
  - status ok!
  - path bad:
    7a8
    > /Users/travis/.sdkman/candidates/ant/current/bin
  - anthome bad:
    1c1
    < /Users/travis/.sdkman/candidates/ant/1.9.9
    ---
    > /Users/travis/.sdkman/candidates/ant/current

This tastes suspiciously like a reincarnation of #19 -- but only on macOS? Does the workaround maybe not work there?

reitzig added a commit that referenced this issue Nov 6, 2019
@reitzig
Copy link
Owner Author

reitzig commented Nov 6, 2019

Turns out it was exactly that, due to sed behaving differently on macOS.

Seems that was the last of it -- ship it!

PS: Developing for macOS without a Mac ... sucks.

@reitzig reitzig closed this as completed Nov 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant