diff options
| author | Eelco Dolstra <e.dolstra@tudelft.nl> | 2007-12-04T11·42+0000 |
|---|---|---|
| committer | Eelco Dolstra <e.dolstra@tudelft.nl> | 2007-12-04T11·42+0000 |
| commit | d4950f207f18e635cc13e3ee33103fd501456384 (patch) | |
| tree | fa02b9398b00df1ea223d15c75f9a4a011d1fed1 /doc/manual/introduction.xml | |
| parent | 6d6c68c0d29310b6eca35f58b1e68f495d6cd33a (diff) | |
* component -> package.
Diffstat (limited to 'doc/manual/introduction.xml')
| -rw-r--r-- | doc/manual/introduction.xml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/manual/introduction.xml b/doc/manual/introduction.xml index 7f7cd11d5a68..d2f23bf44aef 100644 --- a/doc/manual/introduction.xml +++ b/doc/manual/introduction.xml @@ -50,7 +50,7 @@ are complete. In general, when you’re making a package for a package management system like RPM, you have to specify for each package what its dependencies are, but there are no guarantees that this specification is complete. If you forget a dependency, then the -component will build and work correctly on <emphasis>your</emphasis> +package will build and work correctly on <emphasis>your</emphasis> machine if you have the dependency installed, but not on the end user's machine if it's not there.</para> |