diff options
author | 2023-01-18 22:11:32 +0100 | |
---|---|---|
committer | 2023-01-18 22:11:32 +0100 | |
commit | 39d51402f2eaa0ca06cb52ca3f5e1562a3496dbd (patch) | |
tree | e1cad02b28920ee23fca1562fe0aee834086130f /introduction.tex | |
parent | pms.tex: Update copyright years (diff) | |
download | pms-39d51402f2eaa0ca06cb52ca3f5e1562a3496dbd.tar.gz pms-39d51402f2eaa0ca06cb52ca3f5e1562a3496dbd.tar.bz2 pms-39d51402f2eaa0ca06cb52ca3f5e1562a3496dbd.zip |
Whitespace
Signed-off-by: Ulrich Müller <ulm@gentoo.org>
Diffstat (limited to 'introduction.tex')
-rw-r--r-- | introduction.tex | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/introduction.tex b/introduction.tex index 57fb51a..86149b2 100644 --- a/introduction.tex +++ b/introduction.tex @@ -13,9 +13,9 @@ This document does not specify any user or package manager configuration informa \section{Rationale} -At present the only definition of what an ebuild can assume about its environment, -and the only definition of what is valid in an ebuild, is the source code of the latest Portage release -and a general consensus about which features are too new to assume availability. This has several +At present the only definition of what an ebuild can assume about its environment, and the only +definition of what is valid in an ebuild, is the source code of the latest Portage release and +a general consensus about which features are too new to assume availability. This has several drawbacks: not only is it impossible to change any aspect of Portage behaviour without verifying that nothing in the tree relies upon it, but if a new package manager should appear it becomes impossible to fully support such an ill-defined standard. |