On Fri, Aug 3, 2018 at 12:24 AM, Kevin Fenzi <kevin@xxxxxxxxx> wrote:
> I just don't think it's smart to drop the release number
> thing and the fedora-repos-rawhide package.
The number will keep working too. We can make that an alias in
mirrormanager. So, for example if we had this implemented now and we
branched 29 off, '29' would point to the branched release, '30' or
'rawhide' would point to rawhide.
To be fair here, if COPR and other third party inherited the "single repo for all releases, using $releasever" approach as suggested, the number would work for internal Fedora repos (because it's easy to do so in mirrormanager), but it wouldn't work for COPR and other third-party repos (because they don't have a mirrormanager). Of course they could make it work by maintaining symlinks, just as now they can make it work by maintaining symlink - but they don't.
The question is what is the important use case for using a number in repo network requests, if we make it work by default (using releasever=rawhide). Would anyone need to side-step dnf to perform their own calls, and this would complicate the life for them? I don't know, tell me. (We could make the releasever value easily obtainable in that case, either through dnf or through evaluating an rpm macro).
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/HES4WBVWYYIPFL7AWEBLDI756NNGXMNY/
