Tom Lane f201da39ed Make configure prefer python3 to plain python.
This avoids possibly selecting Python 2.x on systems that have
both Python 2 and Python 3.  We used to feel that what "python"
links to is a user choice that we should honor.  However, we're
about to cease support for Python 2, so users will no longer have
any choice of that sort.  This small change is being made ahead
of the big Python-2-ectomy so that we can see how much of the
buildfarm is not yet prepared for that.  Systems with only
Python 2 will continue to build that way, for now.

Discussion: https://postgr.es/m/2872c9a0-4b0a-1354-d5f6-94d6f85ba354@enterprisedb.com
2022-01-19 15:38:58 -05:00
..
2021-09-28 15:26:25 +02:00
2021-11-24 18:32:56 +02:00
2020-07-05 15:37:57 +02:00
2021-07-16 12:39:45 +02:00
2020-10-26 19:17:05 -04:00
2021-09-29 11:56:13 +09:00
2020-02-26 13:05:30 -08:00
2020-03-29 11:15:11 +02:00
2022-01-17 10:16:53 +09:00
2018-10-11 11:43:56 -07:00
2021-01-29 14:09:41 +13:00
2021-12-13 17:33:32 -05:00
2020-07-18 22:43:35 +09:00
2021-04-07 13:52:26 +02:00
2021-12-09 15:20:36 +09:00
2020-10-19 13:48:00 +02:00
2020-06-07 13:18:36 +02:00
2021-07-05 09:36:11 +05:30
2017-10-17 15:10:33 -04:00
2020-07-18 22:43:35 +09:00
2021-07-05 09:36:11 +05:30
2022-01-02 17:06:32 +01:00
2019-10-25 20:39:41 +02:00
2017-10-17 15:10:33 -04:00
2017-10-17 15:10:33 -04:00
2020-07-18 22:43:35 +09:00
2020-10-19 19:28:54 +03:00
2021-07-16 12:39:45 +02:00
2022-01-07 19:04:57 -05:00
2019-09-08 10:27:29 +02:00
2022-01-07 19:04:57 -05:00
2021-08-27 18:20:40 +02:00
2021-01-05 14:26:37 -05:00
2017-10-17 15:10:33 -04:00
2020-08-28 08:19:12 +02:00
2017-10-17 15:10:33 -04:00
2020-12-23 09:33:20 -05:00
2021-07-05 09:36:11 +05:30
2021-06-28 11:31:16 -04:00
2021-06-28 11:31:16 -04:00
2019-09-08 10:27:29 +02:00
2021-09-29 11:56:13 +09:00
2019-03-27 23:10:23 +01:00
2021-07-16 12:39:45 +02:00
2021-12-08 16:54:52 -05:00
2019-09-08 10:27:29 +02:00

<!-- doc/src/sgml/README.links -->

Linking within DocBook documents can be confusing, so here is a summary:


Intra-document Linking
----------------------

<xref>
	use to get chapter/section number from the title of the target
	link, or xreflabel if defined at the target, or refentrytitle if target
        is a refentry;  has no close tag
	http://www.oasis-open.org/docbook/documentation/reference/html/xref.html

linkend=
	controls the target of the link/xref, required

endterm=
	for <xref>, allows the text of the link/xref to be taken from a
	different link target title

<link>
	use to supply text for the link, only uses linkend, requires </link>
	http://www.oasis-open.org/docbook/documentation/reference/html/link.html
	can be embedded inside of <command>, unlike <xref>


External Linking
----------------

<ulink>
	like <link>, but uses a URL (not a document target);  requires
	</ulink>; if no text is specified, the URL appears as the link
	text
	http://www.oasis-open.org/docbook/documentation/reference/html/ulink.html

url=
	used by <ulink> to specify the URL, required


Guidelines
----------

- For an internal link, if you want to supply text, use <link>, else
  <xref>.

- Specific nouns like GUC variables, SQL commands, and contrib modules
  usually have xreflabels.

- For an external link, use <ulink>, with or without link text.

- xreflabels added to tags prevent the chapter/section for id's from being
  referenced;  only the xreflabel is accessible.  Therefore, use xreflabels
  only when linking is common, and chapter/section information is unneeded.