Yeah, this would be a nice feature. What I use right now is a script
specified in the allowed_scms attribute in kojid.conf plus a patch to
kojid to call that script before checking the spec file:
https://gist.github.com/matyasselmeci/8c6e8d03a4e0fb256ec83a1aec2a04aa
-Mat
On 09/10/17 20:48, Neal Gompa wrote:
> Hey all,
>
> I'm trying to figure out how to build Mageia packages using Koji from
> Mageia's distribution SCM. One of the interesting things about this is
> that Mageia uses a Dist-SVN layout. The layout looks something like
> this:
>
>
svn.mageia.org:
> |
> ---- packages
> |
> ---- cauldron
> | |
> | ---- <pkgname>
> | |
> | ---- current
> | |
> | ---- {SOURCES,SPECS}
> |
> ---- (updates|backports)
> |
> ---- <releasever>
> |
> ---- <pkgname>
> |
> ---- current
> |
> ---- {SOURCES,SPECS}
>
> The reason for the layout is because we have other folders there that
> serve other purposes (they are effectively subtrees, and different
> parts of the distribution release toolchain operate on different
> folders per package).
>
> Nearest I can tell, Koji currently expects
> svn:foo/bar/baz/<pkgname>/{SOURCES,SPECS}. Since Koji wants to do the
> checkout itself, is there a nice way to do this without having to do
> ugly patches? Preferably via a configuration item? I really don't want
> to introduce ugly Makefile stuff to make this work, as the layout is
> designed to be friendly to rpmbuild runs.
>
> Thanks in advance and best regards,
> Neal
>