How to create a new registries

[m-kuhn]

I have never done that before (port overlays yes, registries no)

Some questions come to my mind:

basic folder structure
automations (version history, json formatter/linter)
ci checks
If anyone already has a clear idea how to do that before starting some trial and error approach, please speak up now.

By @Neumann-A

basic folder structure

should probably be

/ports
/versions

following main line. It is a bit annoying to have versions in the folders with the ports and other stuff (like repo settings).

adding versions can be done via:
./vcpkg.exe x-add-version --all --overlay-ports=<dir-to-repo>/ports --x-builtin-registry-versions-dir=<dir-to-repo>/versions --x-builtin-ports-root=<dir-to-repo>/ports

but @autoantwort might have more experience setting registries up?

automations

I would like to see v db updates and manifest formatting on merge or have a bot doing that. (Since it is just annoying to manually invoke those.)

ci checks

if the above is done on merge or via a bot. The only required CI checks are actually building stuff if I am not mistaken.

P.S. This is a recovery of a discussion that was started earlier. I deleted the meta repository because the intention was to move this to the org discussions. Only after I realized that org discussions do not exist and are actually linked to the discussions of the meta repository. Sorry for the noise.

[m-kuhn]

I would like to see v db updates and manifest formatting on merge or have a bot doing that. (Since it is just annoying to manually invoke those.)

On merge risks conflicts with other merges happening in parallel. On pr commits interferes with additional pushes. A bot that reacts to comments sounds like a feasible option.

ci checks

if the above is done on merge or via a bot. The only required CI checks are actually building stuff if I am not mistaken.

Yes, I was wondering if gh actions or azure is the way to go and how to determine which ports to check. And if there's maybe already a template.

[m-kuhn]

I am only concerned about the registry right now, first timer troubles

[autoantwort]

I can later setup an example registry where github actions manage everything and you only have to commit stuff

[m-kuhn]

I am definitely happy about any contributions in this direction.

FTR, I am inspiring myself right now with https://github.com/luncliff/vcpkg-registry/tree/main/.github/workflows and https://github.com/msclock/cmake-registry/blob/master/.github/workflows/ci.yml

FTR 2, I was wondering if we should mutualize these with reusing workflows once this stabilizes.

[m-kuhn]

Autoupdating version db is working.

Tests are not yet implemented, see open-vcpkg/qt5-registry#4 for some thoughts

[m-kuhn]

@autoantwort I hardcoded a few tests by installing specific ports (see e.g. https://github.com/open-vcpkg/python-registry/blob/main/.github/workflows/windows.yml#L58) do you have an idea how hard it would be to extend this to systematically test all ports with the logic from the main vcpkg registry?

[autoantwort]

@autoantwort might have more experience setting registries up?

I have added vcpkg x-init-registry some while ago