macports-dev Digest, Vol 176, Issue 7
karl-michael.schindler at physik.uni-halle.de
Mon Apr 5 20:29:45 UTC 2021
> Am 05.04.2021 um 22:17 schrieb macports-dev-request at lists.macports.org:
> Date: Mon, 5 Apr 2021 20:51:23 +0200
> From: Nils Breunese <nils at breun.nl>
> To: MacPorts Developers <macports-dev at lists.macports.org>
> Subject: Re: Desolate Condition
> Message-ID: <E86C6249-27B6-4E4E-A9C2-E3E859882B91 at breun.nl>
> Content-Type: text/plain; charset=utf-8
> 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
Good point. I’ll check the MacPorts docs about creating packages and hope to extend the docs correspondingly.
More information about the macports-dev