diff options
| author |   Ciaran McCreesh <ciaran.mccreesh@googlemail.com> | 2009-07-10 10:41:40 +0100 |
|---|---|---|
| committer | Ciaran McCreesh <ciaran.mccreesh@googlemail.com> | 2009-07-10 10:43:25 +0100 |
| commit | e4defd580d0d64f3704d367acd49c5d97fdbd90e (patch) | |
| tree | 7a6e3adfef0c3bcb9386cfc46f6c00bab73b9c80 /introduction.tex | |
| parent | Change hostile wording (diff) | |
| download | pms-e4defd580d0d64f3704d367acd49c5d97fdbd90e.tar.gz pms-e4defd580d0d64f3704d367acd49c5d97fdbd90e.tar.bz2 pms-e4defd580d0d64f3704d367acd49c5d97fdbd90e.zip | |
Revert "Change hostile wording"
This reverts commit e66186c8f55f528a93706e924f6598f388264809.
Undetermined is a binary property, so something can't be "such an
undetermined standard". Also, there's nothing hostile about
"ill-defined".
Diffstat (limited to 'introduction.tex')
| -rw-r--r-- | introduction.tex | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/introduction.tex b/introduction.tex index 6a0ef6b..3986f57 100644 --- a/introduction.tex +++ b/introduction.tex @@ -18,7 +18,7 @@ and the only definition of what is valid in an ebuild, is the source code of the 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 undetermined standard. +impossible to fully support such an ill-defined standard. This document aims to address both of these concerns by defining almost all aspects of what an ebuild repository looks like, and how an ebuild is allowed to behave. Thus, both Portage and other |