Skip to content

Conversation

JohanbcEkberg
Copy link
Contributor

Might be wise to remove Bash stuff since it has no impact on this course?

@bjornregnell
Copy link
Member

bjornregnell commented Aug 22, 2025

@JohanbcEkberg thanks!
So I guess you don't think it is enough to say very simply to "use instructions för SDKMAN below" for macos beginners? - I mean brew is yet another thing that is not strictly necessary...

@JohanbcEkberg
Copy link
Contributor Author

@JohanbcEkberg thanks! So I guess you don't think it is enough to say very simply to "use instructions för SDKMAN below" for macos beginners? - I mean brew is yet another thing that is not strictly necessary...

As @trilleplay says in the issue. Brew is (in my opinion) very intuitive and easy for beginners on MacOS (and works pretty well on Linux too) so I think we should give it as an option at least.

@bjornregnell
Copy link
Member

OK lets recommend Homebrew for macos.

But I tried brew on linux once a while ago and it interfered with sdkman and cs and other stuff on path so I'd like to recommend SDKMAN for linux.

Although Homebrew is "yet another thing that I don't know what it is" I trust you that it is very good for all macos people to get it started. So lets go for it for macos.

Perhaps we should have Hombrew under its own heading and refer to that, similar to SDKMAN. Or you want it inlined under MacOS as it is THE "standard" on macos? (What about macports or what its called?) @JohanbcEkberg

@JohanbcEkberg
Copy link
Contributor Author

OK lets recommend Homebrew for macos.

But I tried brew on linux once a while ago and it interfered with sdkman and cs and other stuff on path so I'd like to recommend SDKMAN for linux.

Although Homebrew is "yet another thing that I don't know what it is" I trust you that it is very good for all macos people to get it started. So lets go for it for macos.

Perhaps we should have Hombrew under its own heading and refer to that, similar to SDKMAN. Or you want it inlined under MacOS as it is THE "standard" on macos? (What about macports or what its called?) @JohanbcEkberg

I agree that it does interfere with other tools. I suggest that we inline it under MacOS to avoid the issue you are mentioning of installing some things with SDKMAN, CS, etc.

Macports is in my opinion way too complicated for a beginner since it compiles source code while Homebrew just downloads a precompiled binary. That makes macports a bit more flexible but homebrew provides a solution for beginners that "just works".

@bjornregnell
Copy link
Member

OK so go with inlining macos only and we skip mentioning macports at all

@bjornregnell
Copy link
Member

let me know explicitly when you feel ready to merge and all comments been resolved... @JohanbcEkberg
thanks again for contributing this!

@bjornregnell
Copy link
Member

@JohanbcEkberg tyvärr blev det konflikter när jag mergade #883 från @mnordahl --- hoppas du kan fixa dem manuellt?

@JohanbcEkberg
Copy link
Contributor Author

@JohanbcEkberg tyvärr blev det konflikter när jag mergade #883 från @mnordahl --- hoppas du kan fixa dem manuellt?

Fixat!
Det går bra att merge:a nu för min del.

@bjornregnell bjornregnell merged commit bcc2702 into lunduniversity:master Aug 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants