On Fri, Sep 15, 2017 at 10:17 PM, David Walser luigiwalser@yahoo.com wrote:

Koji doesn't expect subdirs of SOURCES and SPECS. It'll do something like this itself: mkdir SPECS mv *.spec SPECS/ mv * (excluding SPECS) SOURCES/

Also, I'm sure we wouldn't be submitting builds with the koji tool itself, as that's a bit unwieldy and you have to give it the full SCM path and stuff. I'm sure Fedora doesn't use the koji tool directly either, but instead has some front end tool that simplifies the syntax for submitting builds and calls koji inside. Also note that Koji allows you to configure exactly what command the server runs when a build is submitted, so the whole thing with the Makefile is the default, but you can customize that. We should be able to make it work with whatever SCM layout we happen to be using.

It does that *only* if SPECS and SOURCES do not already exist. It supports both arrangements. Back when Fedora used CVS, we had that layout.

It is true that Fedora uses a wrapper tool (fedpkg[1]) to interact with Koji, just as Mageia has one (mgarepo[2]) for interacting with Youri. I've already written a small wrapper for Mageia's SVN to use with Koji (mgapkg-koji[3]), but it doesn't work yet because of the aforementioned layout thing...

fedpkg submits the SCM URL to Koji, so Koji needs to be aware of the layout to shuffle things around properly.

Of course, if we do actually switch to Dist-Git, then this whole issue goes away. But I'm not counting on it.

[1]: https://www.mankier.com/1/fedpkg [2]: https://www.mankier.com/8/mgarepo [3]: https://gitlab.com/mdklinux/mgapkg-koji