On Fri, 12 Jul 2024, izder456 wrote:

On your link, it does not say to send the tarball to the mailing list. 
The link you provided is not clearly written and if you look at some recently 
committed new ports in the mailing list - none are tarballs.


> On Wed, 10 Jul 2024 10:57:31 -0700 (PDT)
> "J. Scott Heppler" <shep971@spectrum.net> wrote:
>
>>
>> I'd like to see this port get some traction.  Presently on Current
>> LXQt 2.0, you can't bring in any icons other than breeze for a dark
>> theme.
>>
>> One potential pitfall with the submission is the incorrect format.
>>
>> This link is a little out of date:
>>
>> https://www.openbsd.org/faq/ports/guide.html#:~:text=Submit%20the%20port.,encoded%20to%20the%20same%20address.
>
> From this very link:
>> Submit the port. Create a gzipped tarball of the port directory. You
>> can then either place it on a public HTTP server, sending its URL to ports@openbsd.org, or send the port MIME encoded to the same address.
>
> I sent it as a tgz file.
>
>> In addition to inline mime encoded in the body of the email, the
>> mailing list will now accept the patch, as a *diff, as an attachment.
>>  The  mailing list will display the attached diff but not a
>> compressed, archive file.
>
> AFAIK, *could be wrong*, diffs are more for updates to ports, not
> entirely new ports. I am familiar with making diffs, and have
> ported/updated a few things in this tree already. Thanks anyways.
>
>> Rafael Sadows is all things Qt5/6 and has a full plate.  Getting him
>> to review your *.diff would go a long way.  I think he has commit
>> privileges.
>
> I suppose I'll need to wait till he sees this.
>
> Thanks for the pointers.
>
>
>
>

-- 
J. Scott Heppler

Penguin Innovations

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -


NOTICE: This e-mail message and any attachments may
contain legally privileged and confidential information intended
solely for the use of the intended recipients. If you are not an
intended recipient, you are hereby notified that you have
received this message in error and any review, dissemination,
distribution, copying, or other unauthorized use of this email
and any attachment is strictly prohibited. If you have received
this email in error, please notify the sender immediately and
delete the message and any attachments from your system.