On Thu, Feb 1, 2018, at 10:24 AM, nicolas.mailhot@xxxxxxxxxxx wrote: > > Not directly. It does provide the means to easily rev a spec to a new > code state (version tag or commit), and it makes deps systematic (so > Fedora tooling can accurately detect what is likely to be impacted by a > change). Together, those open the way to use generic Fedora testing > tools to automate build tests. I appreciate the work you're doing here, but I think the right path for golang (indeed for most other language ecosystems) is to autogenerate specs. Like this: https://github.com/clearlinux/autospec plus language-specific plugins basically. Also having all of the golang -devel packages in a single git repository with subdirectories so it's easy to have a single PR affect multiple packages at once. (Of course, this model crosses other things beyond golang). Reference: https://github.com/coreos/coreos-overlay for the latter. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
