> What will RPM do when /usr/share/ssl changes from a directory to a > symlink on an upgrade, if /usr/share/ssl contains non-package-managed > files? Fail to create the symlink, I'd presume? In which case, old > configurations will remain pointing at old files, so no migration is > necessary. Of course, if people *want* to migrate their stuff over they > can do that manually. > > I don't think %post scripts should go moving random user-controlled > files around nor munging configurations because of this change. Agreed. I think this should be flagged in the release-notes but otherwise not an automated event. For things like ssl keys erring on the side of caution makes a lot of sense. -sv
