summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorMatthieu Herrb <matthieu@cvs.openbsd.org>2006-11-30 17:58:49 +0000
committerMatthieu Herrb <matthieu@cvs.openbsd.org>2006-11-30 17:58:49 +0000
commitb47cdecaf219bcde435d6220748109a87e10dafb (patch)
tree2d01e9f68040b8dc13a8b09118550b47c3d0b316 /README
parentfc4de4c3051892d7c1784dc345b13084a45ff86e (diff)
typos and tweaks from bernd@ and todd@.
Diffstat (limited to 'README')
-rw-r--r--README26
1 files changed, 13 insertions, 13 deletions
diff --git a/README b/README
index 3bead848e..aeaa180f3 100644
--- a/README
+++ b/README
@@ -34,14 +34,14 @@ In addition Xenocara uses the following directories:
- dist: contains the Mesa sources, shared by lib and xserver above
- distrib: all binary distribution related tools and data
- etc: mtree(8) data files
-- share: make(1) configuration for xenocara
+- share: make(1) configuration for Xenocara
At the top-level directory two files describe the individual
-components of xenocara:
+components of Xenocara:
- MODULES lists all X.Org components (imported from the X.Org
distribution at http://xorg.freedesktop.org/archive/)
-- 3RDPARTY lists all 3rd party software components provided in Xenora,
+- 3RDPARTY lists all 3rd party software components provided in Xenocara,
either as dependencies of the X.Org software, or as
complements to it to provide a more useable default
environment.
@@ -49,10 +49,10 @@ components of xenocara:
o Compiling and installing
------------------------
-Xenocara is made of more than three hundred of different
-independant packages that need to be build and installed in the right
-order, especially while bootstraping (while /usr/X11R6 is still
-empty). The xenocara Makefiles take care of that using the 'build'
+Xenocara is made up of more than three hundred different
+independent packages that need to be build and installed in the right
+order, especially while bootstrapping (while /usr/X11R6 is still
+empty). The Xenocara Makefiles take care of that using the 'build'
target.
Requirements
@@ -60,7 +60,7 @@ target.
A freshly checked out xenocara tree is buildable without any external
tool. However if you start modifying things in the automake build
system used by many packages, you will need to have the following
-GNU autools packages installed:
+GNU autotools packages installed:
- automake 1.9 (devel/automake/1.9)
- autoconf 2.59 (devel/autoconf/2.59)
@@ -74,8 +74,8 @@ If the SUDO variable points to your sudo(8) binary in /etc/mk.conf,
whenever needed with sudo. Otherwise, you need to run make build as
root.
-If you have installed the full xenocara X sets on your system, you
-don't need to build all of xenocara to patch one element. You can go
+If you have installed the full Xenocara X sets on your system, you
+don't need to build all of Xenocara to patch one element. You can go
to any module sub-directory and run 'make build' from there.
Objdirs
@@ -84,12 +84,12 @@ Xenocara supports objdirs (and it's even the recommended way to build
things). Just run 'make obj' at any level before 'make build' to make
sure the object directory is created.
-XXX support for objdirs need to be improved! XXX
+XXX support for objdirs needs to be improved! XXX
Shadow trees
Alternatively, the old 'lndir(1)' method can still be used to build
-xenocara outside of its source tree. Just don't use 'make obj' in this
+Xenocara outside of its source tree. Just don't use 'make obj' in this
case.
o Regenerating configure scripts
@@ -104,4 +104,4 @@ makefiles skeletons. For that use the following command:
You can also set XENOCARA_RERUN_AUTOCONF in /etc/mk.conf to force
regeneration of configure scripts in every component.
-$OpenBSD: README,v 1.2 2006/11/29 22:25:07 matthieu Exp $ \ No newline at end of file
+$OpenBSD: README,v 1.3 2006/11/30 17:58:48 matthieu Exp $