I think this is OK for inclusion. Normally if an existing package requires a new dependency there is no need to request it for inclusion.

In T10451#199602, @algent wrote:

I think this is OK for inclusion. Normally if an existing package requires a new dependency there is no need to request it for inclusion.

Doesn't it need a repo construction by someone with adequate permissions, though? I might be misremembering.

In T10451#199625, @stalebrim wrote:

Doesn't it need a repo construction by someone with adequate permissions, though? I might be misremembering.

Yes, but you can submit a diff for a non-existent repo. The person merging your stack will just create the corresponding repo when they accept/land your diff.

Something like this usually works:

mkdir newpackage && cd newpackage
git init && git switch -c master
git commit -m "Initial commit" --allow-empty
git remote add origin https://dev.getsol.us/source/newpackage.git

And then you can populate the directory with a makefile and package.yml and you should be off to the races. If arc diff asks just hit enter to accept the default selection of origin/master (idk what the exact question it asks is, been a bit since I've done this).

Note that changing the default branch to master is important, you'll have to fix your commit after you submit your diff if you forget that step.

Very comprehensive response, thanks!

In T10451#199627, @ReillyBrogan wrote:

If arc diff asks just hit enter to accept the default selection of origin/master (idk what the exact question it asks is, been a bit since I've done this).

fatal: Not a valid object name origin/master

I assume this is because the remote doesn't exist yet.