Re: Recommended upgrade procedure for >1 release upgrades

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2016-11-18 09:03 AM, Adam Williamson wrote:
I guess one tweak I would be okay with would be a sort of
weaker-Obsoletes mechanism: some kind of field that provides a hint to
package managers that by default it's OK for the packaging system to
remove a given package if it's blocking another transaction. Then we
could tag all retired packages with that, and people who really want to
keep ancient unmaintained packages around could have a flip to switch
that says 'don't do that'. Of course, it's one more conditional for some
poor sap to maintain.

In fact, now I think about it for two seconds, the 'fedora-obsolete-packages' package can fulfill this role perfectly well. If we make it a policy that all packages which are retired but not specifically obsoleted by anything else be listed as Obsoletes: in that package, then you can decide whether such packages are removed on update/upgrade simply by whether you have that package installed or not.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux