Florian Festi wrote:
seth vidal wrote:
I had a silly thought as the year ticked over last night. - Would it
make sense for us to put in an update nag for yum in yum with a hard
date in it. So, for example, if 3.2.12 is released in march 2008, we
have a check in the startup of the code that says 'if the date is >
march 2011, print out a nag warning to stderr that this version of yum
is quite old and maybe you should look for a newer one or ask your
distribution vendor for an update'. It'd be easy to disable, of course,
but it might be worth while just to catch people like those we know are
still running rhl9 or fc1.
I can't yet see a reason why nagging about yum updates is more
desired/required/acceptable than nagging about updates of any other
program/component.
With yum-updatesd we already have program that can be used to be nagged
about updates. If there is something missing in yum-updatesd (yes, I
know it doesn't have a very glory history) we should add it there.
In addition it should be the decision of the distribution when and if at
all to update any given component - including yum. Some distributions
try to be stable over 7 years (some non Linux OS have even much longer
commitments) - so we will break their update model.
What might make sense is nagging on a release level: Nag about End of
Live for Fedora X for example. But this should be done outside of yum IMHO.
+1
Tim
_______________________________________________
Yum-devel mailing list
[email protected]
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
