Okay … speaking under correction, but I believe all the existing 3rd-party repos are primarily targeting gcc2-hybrid. There certainly is a space out there for a repo that concentrates on pure x86_64. bbjimmy has a tutorial on how to set it up: http://fatelk.com/repo/repo.html. IIRC Lelldorin’s repo has a GUI app to manage a repo.
X86_64 is in a bit of a chicken-and-egg situation IMHO. Nobody is writing or porting for it because it is not going to be the official format of the next release, but it is not going to be the format of a next release unless there is overwhelming user demand and plenty of apps.
But you don’t really NEED a repo right away. I would suggest that at first, you simply post your HPKGs to your website to see if there is a demand for what you have in mind. Get people to download the HPKG and double-click to install. The smaller repos generally have a web interface of their own in addition to being available via the pkgman command, Haikudepot app and the Haikudepot web app. e.g http://fatelk.com/repo/ As the number of packages in your repo grows, that is no longer maintainable. Trust me, I’ve tried.
You could also ask the existing user community what they think of the idea on the Haiku Facebook group: https://www.facebook.com/groups/haikuosgroup - There are people there who do not necessarily read this forum.
Then you can decide whether to start your own repo or to work via haikuports. Or both. For example, you could use your own repo as a testing branch before you commit to haikuports. No, you don’t have to do that, I’m just showing that there’s considerable flexibility in the system.
The best place to find the existing repo managers and ask for advice is BeShare. Some of us are more territorial than others. That’s not a point of criticism, BTW. You are most welcome to download my entire repo and produce x86_64 versions of everything that includes source code. But some of the others prefer a little more control over where their material ends up, so ask first.
One thing we are pretty good about is advertising each others’ repos on our websites, so I don’t think discoverability would be a problem.