Karl-Michael Schindler <karl-michael.schind...@physik.uni-halle.de> wrote:
> This indicates the first problem: Brew is often better represented on > homepages of other software than MacPorts. The task to tackle is to find a > person or form a team going after this. A more scalable solution would be for port maintainers to check the upstream docs for the ports they maintain and contribute a snippet on how to install the software via MacPorts if not already present. Usually all this takes is a simple merge request. I think this is a great idea and I’ve been doing this for my ports. Examples from the Spring Boot documentation: https://docs.spring.io/spring-boot/docs/current/reference/html/getting-started.html#getting-started-macports-cli-installation People will even start copying these MacPorts installation instructions into blog posts and educational materials. Examples of ’sudo port install kotlin’: https://www.google.com/search?q=%22sudo+port+install+kotlin%22 Apparently it was even copied into an O’Reilly book: https://www.oreilly.com/library/view/kotlin-programming-by/9781788474542/86027be9-71a7-4afc-8354-51fceeb741d9.xhtml Nils.
