+1, though see https://praiskup.fedorapeople.org/Screenshot_20180124_184936.png
from #185, with the next release it should be trivial to hire rust2rpm:

1
2
3

#! /bin/sh
rust2rpm <pkgname>
spectool -g *.spec

Seems to be ready-for-testing on dev instance:
http://copr-fe-dev.cloud.fedoraproject.org/coprs/ngompa/snapcore-el7/add_build_custom/

It'd be nicer if it worked the same way the RubyGem and PyPI implementations do, and I'm not sure it's a good idea to allow custom scripts like that. Wouldn't that be a security risk?

The custom script is run on temporary VM (not shared among users).
Note that rpmbuild -bs *.spec also can execute "custom" script through
%(...) macros.. so no difference from py2rpm, etc.. Yes, you are able to
break your own build machine in copr in the worst case.

Of course it would be better to have native support for other stacks, I'm just pointing out a work-around.

I am all for native support. But first we have to resolve how to get notifications from upstram. We have support for upstream monitoring, which we prefer, but this currently emits only messages for registred projects. We are waiting for support non-registered projects, which is prommised "soon" for quite long time :(

Duplicate #154

This issue has been migrated to GitHub: https://github.com/fedora-copr/copr/issues/246