Re: Submitting ports with required dependencies

New ports in an attached tar please, not as diffs. Updates preferably as diff -u (inline if you know how to do that without them getting mangled, or as attachments). If there are just a couple then in one mail is often easier to keep track of. Don't have too many in flight at once (especially at first, feedback might be common to several ports).

-- 

  Sent from a phone, apologies for poor formatting.

On 4 January 2025 00:18:21 Rane Hebden <rane+openbsd@junkyard.systems> wrote:

I've done some reasearch on this already, but I was curious if anyone

had any guidance on the best way to submit a new port which requires

several other new ports as dependencies?

I can see a few options, and would be interested in what would make

reviewing and potentially giving an OK to the new ports easiest?

Should each port be submitted separately to ports@, with or without

the context that the port is required as a dependency for another port?

Or is it best to submit all patches for all dependency and the main port

at the same time, in the same mail? I assume with patches as attachments

rather than inline?

Thanks!