[Frugalware-darcs] pacman: changes to Frugalbuild's man page

[VMiklos]

Darcsweb-Url: http://darcs.frugalware.org/darcsweb/darcsweb.cgi?r=pacman;a=darcs_commitdiff;h=20061121111243-e2957-d01e960f77d6d106fa9c81e9a096fdf01de92e29.gz;

[changes to Frugalbuild's man page
VMiklos <vmiklos at frugalware.org>**20061121111243
 From: Russell Dickenson <russelldickenson at gmail.com>
] {
hunk ./doc/FrugalBuild.8 40
-build took. After you built binutils, you should update your /etc/makepkg.conf:
+build took. After you have built binutils, you should update your
+/etc/makepkg.conf:
hunk ./doc/FrugalBuild.8 47
-successful builds, and this SBU value will be equal on anyone's machine.
+successful builds, and this SBU value will be equal on everyone's machine.
hunk ./doc/FrugalBuild.8 50
-address to the third line. If you don't plan to maintain the package just wrote
-the FrugalBuild, then write Contributor instead of Maintainer, and then someone
-can take it and will add his/her line later. Other lines like "Modified by" are
-not allowed. Use the darcs patch comments to mention others if you wish.
+address on the third line. If you just wrote the FrugalBuild don't plan to 
+maintain the package , then write Contributor instead of Maintainer, and then
+someone can take it and will add his/her line later. Other lines like
+"Modified by" are not allowed. Use the darcs patch comments to mention others
+if you wish.
hunk ./doc/FrugalBuild.8 65
-the project's homepage or manpage. Try to keep the lenght under 80 chars.
+the project's homepage or manpage. Try to keep the length under 80 chars.
hunk ./doc/FrugalBuild.8 68
-depends() means the other package is required for building and using the
-current one. If the dependency is runtime-only, then use rodepends(), if
+depends() lists those packages required for building and using the current
+one. If the dependency is runtime-only, then use rodepends(), if
hunk ./doc/FrugalBuild.8 72
-The next line is a special Finclude commands which allows you to inherit
+The next line is a special Finclude command which allows you to inherit
hunk ./doc/FrugalBuild.8 74
-under /source/include. The "util" scheme always included, since its
+under /source/include. The "util" scheme is always included, since its
hunk ./doc/FrugalBuild.8 79
-if the inherited one is not sutable for you.
+if the inherited one is not suitable for you.
hunk ./doc/FrugalBuild.8 81
-The groups() array's first element can't be omitted, and it should be a valid
+The groups() array's first element is mandatory, and it should be a valid
hunk ./doc/FrugalBuild.8 87
-generating package databases. If you are not able to provide a binary package
-for a given arch, don't include that in archs()! For example, no matter if
-the package could be compiled in x86_64, if you haven't compiled it yourself,
-don't include it. If you're sure it won't be available on a given arch (for
-example it's written in x86 asm), then use !arch, for example !x86_64.
+generating the package databases. If you are not able to provide a binary
+package for a given arch, don't include that in archs()! For example, no matter
+if the package could be compiled in x86_64, if you haven't compiled it
+yourself, don't include it. If you're sure it won't be available on a given
+arch (for example it's written in x86 asm), then use !arch, for example
+!x86_64.
hunk ./doc/FrugalBuild.8 95
-is to prevent compiling from wrong sources, especially when the build is
+is to prevent compiling from corrupt sources, especially when the build is
hunk ./doc/FrugalBuild.8 101
-cross-compile on a faster machine for a slower architecture. Until the package
+cross-compile on a faster machine for a slower architecture. If the package
hunk ./doc/FrugalBuild.8 108
-want to do anything special, probably you don't have to specify anything, as
+want to do anything special, you probably don't have to specify anything, as
hunk ./doc/FrugalBuild.8 116
-will prepare some documentation. It will
-then strip debugging info from libraries and binaries and generate a meta-info
-file.  Finally, it will compress everything into a .fpm file and leave it
-in the directory you ran \fBmakepkg\fP from.
+will prepare some documentation. It will then strip debugging info from
+libraries and binaries and generate a meta-info file.  Finally, it will compress
+everything into a .fpm file and leave it in the directory from which you ran
+\fBmakepkg\fP.
hunk ./doc/FrugalBuild.8 165
-$pkgname.install install and will use it if it's present.
+$pkgname.install script and will use it if it's present.
hunk ./doc/FrugalBuild.8 272
-This array defines on which architectures the given package is avalibable.
+This array defines on which architectures the given package is available.
hunk ./doc/FrugalBuild.8 303
-logrotate doesn't requires to have dcron installed.) Packages in this list
+logrotate doesn't require that dcron be installed.) Packages in this list
hunk ./doc/FrugalBuild.8 351
-This system lacks of the ability to control the list of installed packages
-during the build on the system of a packager, the given compiled package maybe
-linked itself to an extra installed library. This way we can't really control
-the list of real dependencies. For example if libquicktime is installed from
-source on my system, then mplayer or any other program can link itself to that,
-and so that depends() will be incorrect. Or if I have the closed source binary
-NVidia drivers installed, some programs link tho NVidia's libraries.
+This system lacks the ability to control the list of installed packages
+during the build on the system of a packager. Because of this, the given
+compiled package may link itself to an extra installed library. This way we
+can't really control the list of real dependencies. For example if libquicktime
+is installed from source on my system, then mplayer or any other program can
+link itself to that, and so that depends() will be incorrect. Or if I have the
+closed source binary NVidia drivers installed, some programs link to NVidia's
+libraries.
hunk ./doc/FrugalBuild.8 360
-Of course there is a sollution to avoid this, to use a real chroot instead of a
-simple fakeroot. What is this means? The followings:
+Of course there is a solution to avoid this, to use a real chroot instead of a
+simple fakeroot. What does this mean? The following:
hunk ./doc/FrugalBuild.8 368
-devel-core' should show you the actial list. (We try to change this list rarely
+devel-core' should show you the actual list. (We try to change this list rarely
hunk ./doc/FrugalBuild.8 373
-that consits of base packages only. This /var/chroot is fully separated from
+that consists of base packages only. This /var/chroot is fully separated from
hunk ./doc/FrugalBuild.8 383
-installed depends() and makedepends(). This ensures us not to build from
-scratch the core chroot.
+installed depends() and makedepends(). This ensures you do not have to build
+the core chroot from scratch.
hunk ./doc/FrugalBuild.8 387
-build packages for a different Frugalware version. This is quite efficent when
+build packages for a different Frugalware version. This is quite efficient when
hunk ./doc/FrugalBuild.8 390
-If the build is failed, the working directory will not be deleted, you can find
+If the build fails, the working directory will not be deleted, you can find
hunk ./doc/FrugalBuild.8 399
-Package splitting means moving out a list of specifed files to subpackages (like
+Package splitting means moving out a list of specified files to subpackages (like
hunk ./doc/FrugalBuild.8 408
-now all the directives has their subfoo equivalent:
+now all the directives have a subfoo equivalent:
}