New Port request: Vapor.code filed, what else is needed?

[lars.sonchocky-helldorf at hamburg.de]

Hi everybody,

made a PR: https://github.com/macports/macports-ports/pull/34081

kind regards,

	Lars

> Am 16.08.2026 um 23:24 schrieb lars.sonchocky-helldorf--- via macports-dev <macports-dev at lists.macports.org>:
> 
> Hi everybody,
> 
> I did something with the help of Googles AI:
> 
> https://share.google/aimode/kyjFcW4qeKyeNJ7TN
> 
> The result is here:
> 
> <Portfile>
> 
> for devel/vapor-toolbox tested and working. Should I create a pull request for this?
> 
> TIA,
> 
> 	Lars
> 
>> Am 16.08.2026 um 19:38 schrieb Mark E Anderson <mark at macports.org>:
>> 
>> I'd sign up for macports-dev for sure, we can help over there. It's easiest if you give it the ol' college try and we can sorta give some tips. Also guide.macports.org is invaluable if a bit dated here and there. The wiki at trac.macports.org also has some recipes. Feel free to reach out to me as well, this is one I'd love to have but didn't really want to do/maintain.
>> 
>> —Mark
>> Macports Wiki Page <https://trac.macports.org/wiki/mark> | GitHub <https://github.com/markemer> | Blog <https://emer.net/>
>> 
>> On Sun, Aug 16, 2026, at 1:07 PM, Bill Cole wrote:
>>> On 2026-08-16 at 11:57:30 UTC-0400 (Sun, 16 Aug 2026 17:57:30 +0200)
>>>   <lars.sonchocky <http://lars.sonchocky/>-helldorf at hamburg.de <mailto:-helldorf at hamburg.de>>
>>> is rumored to have said:
>>> 
>>> > Hi Bill,
>>> >
>>> >> Am 16.08.2026 um 15:48 schrieb Bill Cole 
>>> >> <macportsusers-20171215 at billmail.scconsult.com <mailto:macportsusers-20171215 at billmail.scconsult.com>>:
>>> >>
>>> >> On 2026-08-16 at 07:47:02 UTC-0400 (Sun, 16 Aug 2026 13:47:02 +0200)
>>> >> lars.sonchocky <http://lars.sonchocky/>-helldorf--- via macports-users 
>>> >> <lars.sonchocky <http://lars.sonchocky/>-helldorf at hamburg.de <mailto:-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 <http://vapor.codes/> ( https://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.
>>> >
>>> > I can definitely try to. Never did this before, but somewhen is the 
>>> > first time. Would it be o.k. to post preliminary results here on the 
>>> > list to get help in certain situations?
>>> 
>>> I am not any sort of authority on that, but I do recall users doing so 
>>> here and getting help from project members. There is also a 
>>> 'macports-dev' list which is focused on port development, and which may 
>>> get more attention from the active developers.
>>> 
>>> 
>>> -- 
>>>   Bill Cole
>>>   bill at scconsult.com <mailto:bill at scconsult.com> or billcole at apache.org <mailto:billcole at apache.org>
>>>   (AKA @grumpybozo at toad.social <mailto:grumpybozo at toad.social> and many *@billmail.scconsult.com 
>>> addresses)
>>>   Please keep discussion mailing list replies *on-list*
>>>   Not Currently Available For Hire
>>> 
>> 
>> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20260817/c1794fe7/attachment-0001.htm>