New Port request: Vapor.code filed, what else is needed?
Bill Cole
macportsusers-20171215 at billmail.scconsult.com
Sun Aug 16 13:48:54 UTC 2026
On 2026-08-16 at 07:47:02 UTC-0400 (Sun, 16 Aug 2026 13:47:02 +0200)
lars.sonchocky-helldorf--- via macports-users
<lars.sonchocky-helldorf at hamburg.de>
is rumored to have said:
> Hi there,
>
> now quite a while ago I filed this port request:
>
> https://trac.macports.org/ticket/74247
>
> for Vapor.codes ( https://vapor.codes/ ) but nothing happened on that
> report until now.
>
> Was it sufficient if I like to have a port of this to file this
> request or is any other action needed?
The only missing piece is a working port implementation and someone with
commit rights to commit it.
> The port should be easily doable, I compiled it manually in a few
> steps:
>
> https://forums.swift.org/t/vapor-4-and-macports/34365/16
Then you would be the ideal person to write the port.
In my experience, the way to get a fix into MacPorts is to provide
working code. As far as I know, no one is paid to do work on MacPorts
and no one has committed themselves to addressing all requests for new
ports.
--
Bill Cole
bill at scconsult.com or billcole at apache.org
(AKA @grumpybozo at toad.social and many *@billmail.scconsult.com
addresses)
Please keep discussion mailing list replies *on-list*
Not Currently Available For Hire
More information about the macports-users
mailing list