Only do update checking in binary builds

Distro packages and source builds will no longer do update checking.
Remove the packaging defaults instructions since they are not needed
any more. The shell integration scripts shouldnt be installed system
wide anyway.

docs/build.rst

@@ -174,29 +174,3 @@ servers into which they ssh, without needing to install all of |kitty|.
 
 This applies to creating packages for |kitty| for macOS package managers such as
 Homebrew or MacPorts as well.
-
-
-Changing defaults for packages
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-|kitty| has its defaults chosen to be suitable for a standalone distributable.
-If you are packaging it a few of these might need to be changed.
-
-update-checking
-   |kitty| has its own update check mechanism, if you would like to turn
-   it off for your package, use::
-
-       ./setup.py linux-package --update-check-interval=0
-
-shell-integration
-   |kitty| by default injects its :ref:`shell_integration` code into the user's
-   shell using environment variables. For a package, it might make more sense
-   to distribute the shell integration scripts into the system-wide shell
-   vendor locations. The shell integration files are found in the
-   :file:`shell-integration` directory. Copy them to the system wide shell
-   vendor locations for each shell, and use::
-
-       ./setup.py linux-package --shell-integration=enabled\ no-rc
-
-   This will prevent kitty from modifying the user's shell environment to load
-   the integration scripts.

docs/changelog.rst

@@ -69,6 +69,9 @@ Detailed list of changes
 
 - :ac:`select_tab`: Use stable numbers when selecting the tab (:iss:`4792`)
 
+- Only check for updates in the official binary builds. Distro packages or source builds will no longer check for updates, regardless of the
+  value of :opt:`update_check_interval`.
+
 
 0.24.4 [2022-03-03]
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~