On Thu, Dec 6, 2012 at 2:54 PM, Nick Coghlan <ncogh...@gmail.com> wrote:
> On Thu, Dec 6, 2012 at 1:12 PM, Daniel Holth <dho...@gmail.com> wrote: > >> Makes sense. How about calling it Replacement. 0 or 1? >> > > Hah, you'd think I'd have learned by now to finish reading a thread before > replying. It will be nice to get this addressed along with the other > changes :) > > (FWIW, Conflicts and Obsoletes are messy in RPM as well, and especially > troublesome as soon as you start enabling multiple upstream repos from > different providers. The metadata problem is handled by prebuilding indices > when the repo changes, but that's still more work for the server, and more > work for clients) > > >> Replacement (optional) >> :::::::::::::::::::::: >> > > > I like verb forms like Obsoleted-By or Replaced-By, as the noun form is > ambiguous about the direction of the change. Since the field being replaced > is Obsoletes, Obsoleted-By makes sense. > Although Replaced-By would be fine as well - it's certainly much easier to say than the mouthful that is Obsoleted-By. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
