On Thu, Feb 09, 2012 at 06:46:45AM -0500, Martin Sivak wrote: > Although this might be the only simple and possible solution at this moment, I do not agree with it. We are introducing another version specific behaviour and hardcoded paths to scripts outside of our control to anaconda source. That is violating one of our long term goals of making anaconda independent on the product version. > > We discussed another kickstart script sections and fedora-release.rpm (or repodata file, ..) as a container for the release related scripts ages ago. What will we do in F18 when upgrade from F16 and F17 will need to be supported at the same time? The code checks the links, but what if someone comes with something even more wild? > > If we manage to get this kind of information to the repository, for example in the form of repodata/updates/<from-version>.ks with %prechroot script section, we might be able to do stuff like conversion to systemd, usrmove, ... without us being responsible for the code and without being tied to one particular version. In the future upgrades are going to be handled by preupgrade only so we can remove this hack from Anaconda in F18. -- Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA (PST8PDT)
Attachment:
pgp2vgOppUWHG.pgp
Description: PGP signature
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
