> > And why shouldn't we be? This is taking us right back down the road of > > tying a specific version of anaconda to a specific installation set that > > we've been working so hard to get away from for the past several > > releases. > > ... if someone wants to enable rawhide, they can still do so manually, > by adding or editing the repo. ...which is a significantly higher barrier than checking a box. What is the actual concern here with allowing people to enable rawhide? > anaconda's already tied to a specific installation set, just from > the fedora-release it's composed with. It's as tied to a specific installation set as it has to be, yes, but that's even still aggravating for me. fedora-release doesn't really have anything to do with that aside from specifying a "product". The version itself is going to be what gets substituted in for $releasever in the .repo files. And that's controlled by the compose tools, not by fedora-release. - Chris _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
