(original) (raw)

How to use Obsoletes:


The author of B decides A is obsolete.

A releases an empty version of itself that Requires: B

B Obsoletes: A


The package manager says "These packages are obsolete: A". Would you like to remove them?

User says "OK".


On Wed, Nov 21, 2012 at 2:54 AM, Stephen J. Turnbull <stephen@xemacs.org> wrote:

PJ Eby writes:
\> On Wed, Nov 21, 2012 at 12:00 AM, Stephen J. Turnbull <stephen@xemacs.org>wrote:

> > What I care about is when I'm using Gorgon, and there's something
\> > "better" (or worse, "correct") to use in my application.
\>
\> Hence my suggestion for an Obsoleted-By field, in which Gorgon would be
\> able to suggest alternatives.

My bad, my precise intention was to follow up on your idea (which,
credit where credit is due, I had \*not\* hit upon independently). I
should have made that clear.

(I really shouldn't be answering English email at a Japanese-speaking
conference, my brain thinks it knows what it's doing but shirazuni $BF|(B
$BK\\J82=$,@w$\_9\~$\`(B....)

\> > It might be a good idea to have a just-like-Amazon
\> >
\> > While-This-Package-Is-Great-You-Might-Also-Consider:
\> >
\> > field.
\>
\> Yeah, that's basically what Obsoleted-By is for.

Well, Obsoleted-By is pretty strong language for suggesting possible
alternatives. But I suspect that few projects would really want to be
suggesting competitors' products \*or\* their own oldie-but-still-goodie
that they'd really like to obsolete ASAP (put an Obsoleted-By line in
every Python 2 distribution, anyone? :-)
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
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/dholth%40gmail.com