On Thu, Oct 17, 2013 at 10:54:44AM -0400, Paul Wouters wrote: > >>There's no reason to kill the package entirely. Some people still > >>want to use it despite the current issues. So just don't install it > >>by default. Reducing everything down to absolutes isn't helpful. > >Agreed, there's no reason to kill it entirely. Let people opt-in if > >they wish to install it later & understand the cost/benefit tradeoff. > How do we make it go away on the installs it currently affects badly? > Do we add Conflict: to some packages (eg FIPS capable ones) ? If we wanted to do this, changing 'PRELINKING=no' in /etc/sysconfig/prelink in a package update would do it -- the config file is marked as 'noreplace', but if the file hasn't been edited locally, it would be overwritten with the updated one. Then, at the next cron run, prelink would undo the prelinking. I'm not sure if this is the route we should take, or if installation of the package should default to it being active; just putting this out there as an option. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm@xxxxxxxxxxxxxxxxx> -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct