kparal added a new comment to an issue you are following:
``
Please also note that COPR already can use numbered repos for Rawhide
(i.e. having 29/ dir instead of rawhide/, and then using $releasever in their universal
repo file). Instead they opted for the same approach Fedora infra uses, i.e. having a
specific rawhide repo file with rawhide/ dir hardcoded). I don't know whether they
simply copied Fedora infra approach or it was a conscious decision that made their
implementation easier. My goal is to make all this simpler and consistent, and that's
why I suggested changing $releasever to rawhide, instead of keeping it as a number and
convincing everyone to support it in their repo dir structure. We can definitely consider
the latter approach as well, though.
I asked COPR devs at
https://pagure.io/copr/copr/issue/267#comment-510456 whether they
would consider using this approach (a numbered dir even for rawhide), and so far they seem
to be on board with it, if it is the same approach Fedora Releng uses. So if we can make
sure MirrorManager can handle `repo=NN` requests even for Rawhide (which was already
implemented in
https://pagure.io/releng/issue/7398#comment-502442 , but just temporarily
for this particular release; we'd need to make sure it works in the future as well),
and COPR implements this on their side, maybe we don't need any changes to
`fedora-release` as proposed in this ticket at all.
If we use $releasever=NN (and use $releasever in repo URLs), it means
that in order to keep following rawhide on your machine, you'll need to make manual
changes twice a year (during Branching points), exactly at the right time.
It occurred to me that this might have a pretty elegant solution. Let's say that by
default `fedora-repos` are installed, which use `$releasever` in repo URLs. Those machines
would automatically get converted from Rawhide to Branched after branching. However, if
you disabled those repos and installed `fedora-repos-rawhide` (which have `repo=rawhide`
hardcoded in metalink URLs and baseurls), then such a machine would always stay on
Rawhide. So you would actually have a way to avoid manual changes during branching, you
could choose in advance which path to follow. This approach looks like the best of both
worlds, honestly.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7445