clime added a new comment to an issue you are following:
``
Thank you @clime for a great picture, I very appreciate the effort
:-) The right side doesn't show the fact, though, that Rawhide still has a number
that's getting bumped at every branch point. And that number is actually used
everywhere except repo requests (and that's just because the rawhide string is
hardcoded there). The reason is that most specs and tools are based on and mandate using
numbers. It's true for /etc/os-release, it's true for spec files (if %{fedora}
> 20). And that's the root of my issues when doing automation work, the system
claims to be a number if many areas, but network repos are only accessible under a string
label, and I need to maintain the mapping in all our tooling and make sure I update it
everywhere at a precisely the right time.
In Proposed solution 1, I tried to fix this by making sure the special knowledge for
network requests isn't needed (at least when initiated from the system). Instead of
sending releasever=NN it would send releasever=rawhide. It should be the most compatible
change for COPR devs - you can keep rawhide/ dirs on server, you don't need to
maintain rawhide -> NN/ symlinks, it's backward compatible, and you can simplify
your repo files (you no longer need to have a special repo file for Rawhide). @clime, am I
missing some disadvantages for COPR?
No, I think that's a very good description. As you say, the solution no. 1 looks the
best to us from compatibility point of view.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7445