search

ballerina-platform / ballerina-distribution

Apache License 2.0
155 stars 192 forks source link

[Proposal] Add support for MacPorts package manager #3053

Open conradwt opened 6 years ago

conradwt commented 6 years ago

Description:

Add support for installing Ballerina via MacPorts

Steps to reproduce:

N/A

Affected Versions:

N/A

OS, DB, other environment details and versions:

macOS 10.14

Related Issues (optional):

N/A

Suggested Labels (optional):

macOS/Package Management

Suggested Assignees (optional):

I would be interested in building a MacPorts Portfile for the Ballerina Language.

rasika commented 6 years ago

@conradwt For Mac users; we currently support Homebrew package manager which you can install ballerina using brew install ballerina. Will add the supporting for the MacPort into our future roadmap.

conradwt commented 6 years ago

@rasika I can probably build a port for Ballerina being that I have some experience with building Portfiles for MacPorts.

rasika commented 6 years ago

@conradwt +1 to create a Portfile. Sorry, I am new to MacPorts eco-system; I am wondering how we can update Portfile when releasing a new ballerina version. Is it sufficient to send a PR to https://github.com/macports/macports-ports ?

conradwt commented 6 years ago

@rasika Yes, you’ll need to submit a PR to update the Portfile and they have a very fast review process (I.e. within 12 - 24 hours). There may be a way to auto generate the PR using other tools.

rasika commented 6 years ago

@conradwt Cool thanks for the info. Please let us know once you completed the MacPorts Portfile. You can refer Ballerina Homebrew formula if you need.

conradwt commented 6 years ago

@rasika Wil post here when it has been completed.

rasika commented 5 years ago

@conradwt Did you able to complete this? Let us know if you faced any blockers

conradwt commented 5 years ago

@rasika This has not been completed because I have been focused on the day job. However, I'll find some time this weekend to complete this issue.

jimk-osu commented 5 years ago

+1 for this. Through working with one of our devs we found that the brew package installation doesn't seem to be linking the language server with the VS Code extension. Our countermeasure was to use the pkg installation.