From 5f887ca934588a6add6b088eb652f4eaf0cb7bcc Mon Sep 17 00:00:00 2001 From: Rylan Polster Date: Mon, 28 Dec 2020 11:28:17 -0500 Subject: [PATCH] docs: clarify formula deprecation conditions Co-Authored-By: Mike McQuaid --- docs/Deprecating-Disabling-and-Removing-Formulae.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Deprecating-Disabling-and-Removing-Formulae.md b/docs/Deprecating-Disabling-and-Removing-Formulae.md index ee7bfd1b9a..6261e71cd9 100644 --- a/docs/Deprecating-Disabling-and-Removing-Formulae.md +++ b/docs/Deprecating-Disabling-and-Removing-Formulae.md @@ -14,7 +14,7 @@ This general rule of thumb can be followed: If a user attempts to install a deprecated formula, they will be shown a warning message but the install will proceed. -A formula should be deprecated to indicate to users that the formula should not be used and may be disabled in the future. Deprecated formulae should still build from source and their bottles should continue to work. These formulae should continue to receive maintenance as needed to allow them to build. +A formula should be deprecated to indicate to users that the formula should not be used and will be disabled in the future. Deprecated formulae should be maintained by the Homebrew maintainers so they can still build from source and their bottles continue to work (even if unmaintained upstream). If this is not possible, they should be disabled. The most common reasons for deprecation are when the upstream project is deprecated, unmaintained, or archived.