SliTaz Repositories

     1.1 --- a/doc/receipts-v2.md	Sat Dec 23 15:03:39 2017 +0200
     1.2 +++ b/doc/receipts-v2.md	Fri Dec 29 13:05:43 2017 +0000
     1.3 @@ -373,8 +373,8 @@
     1.4  }
     1.5  ```
     1.6  
     1.7 -You should not use `fix libtool` if you not see file named `libtool` in the root
     1.8 -of the sources tree after the `configure` done. It will not lead to an error,
     1.9 +You should not use `fix libtool` if you do not see a file named `libtool` in the root
    1.10 +of the sources tree after the `configure` is done. It will not lead to an error,
    1.11  although there will be no sense in it.
    1.12  
    1.13  You can check dependencies of separate files using one of the next methods:
    1.14 @@ -385,7 +385,7 @@
    1.15  readelf -d /path/to/file | grep NEEDED
    1.16  ```
    1.17  
    1.18 -You can check dependencies of entire package using the command:
    1.19 +You can check dependencies of an entire package using the command:
    1.20  
    1.21  ```bash
    1.22  cook package_name --deps
    1.23 @@ -410,21 +410,21 @@
    1.24  This is a separate and complex issue.
    1.25  
    1.26  Dependency info may be extracted from `.pc`, `.la` and `.h` files. Extracting
    1.27 -dependencies from the header files (`.h`) is non-trivial task due to conditional
    1.28 +dependencies from the header files (`.h`) is a non-trivial task due to conditional
    1.29  branching and can not be realized using simple tools.
    1.30  
    1.31  As for `.la` files — Gentoo
    1.32  [recommend](https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Handling_Libtool_Archives)
    1.33  to remove them in most cases. As they stated, `.la` files may be useful only
    1.34 -for static libraries (`.a` files). Currently, dependency tracking tool doesn't
    1.35 -use `.la` files unless you provide special argument `--la`:
    1.36 +for static libraries (`.a` files). Currently, the dependency tracking tool doesn't
    1.37 +use `.la` files unless you a provide special argument `--la`:
    1.38  
    1.39  ```bash
    1.40  cook fontconfig --deps --la
    1.41  ```
    1.42  
    1.43 -It turns that `.pc` files are the only development files that describe
    1.44 -dependencies of development packages. Usually `configure` script checks
    1.45 +It turns out that `.pc` files are the only development files that describe
    1.46 +dependencies of development packages. Usually the `configure` script checks
    1.47  dependencies using something like this:
    1.48  
    1.49  ```bash
    1.50 @@ -432,8 +432,8 @@
    1.51  pkg-config --exists --print-errors "xrender >= 0.6"
    1.52  ```
    1.53  
    1.54 -Dependency tracking tools tries to find the package that contains required
    1.55 -libraries, then to determine `*-dev` package that corresponds to found package.
    1.56 +Dependency tracking tools try to find the package that contains required
    1.57 +libraries, then determine a `*-dev` package that corresponds to the found package.
    1.58  
    1.59  For example, file `/usr/lib/pkgconfig/cairo.pc` contains the line:
    1.60  
    1.61 @@ -443,7 +443,7 @@
    1.62      xcb >= 1.6   xcb-render >= 1.6   xrender >= 0.6   x11   xext
    1.63  ```
    1.64  
    1.65 -Finding next files shows the dependencies:
    1.66 +Finding the next files shows the dependencies:
    1.67  
    1.68  ```
    1.69  gobject-2.0.pc   glib-2.0.pc   pixman-1.pc   fontconfig.pc   freetype2.pc
    1.70 @@ -462,7 +462,7 @@
    1.71  Libs: -L${libdir} -lapr-${APR_MAJOR_VERSION} -luuid -lrt -lcrypt  -lpthread -ldl
    1.72  ```
    1.73  
    1.74 -Finding next files shows the runtime dependencies and then full dependencies;
    1.75 +Finding the next files shows the runtime dependencies and then full dependencies;
    1.76  `*-dev` packages are the full packages.
    1.77  
    1.78  ```
    1.79 @@ -476,8 +476,8 @@
    1.80  
    1.81  ```
    1.82  
    1.83 -Note, sometimes required files may be found in the two or many packages, for
    1.84 -example, `libdl.so` exists therein packages:
    1.85 +Note, sometimes required files may be found in two or more packages, for
    1.86 +example, `libdl.so` exists within packages:
    1.87  
    1.88    * `glibc-base`
    1.89    * `uclibc-armv4eb`

     2.1 --- a/modules/compressor	Sat Dec 23 15:03:39 2017 +0200
     2.2 +++ b/modules/compressor	Fri Dec 29 13:05:43 2017 +0000
     2.3 @@ -85,7 +85,7 @@
     2.4  	find $fs -type f \
     2.5  	| while read i; do
     2.6  		# output of `readelf -h <file> is human-readable information,
     2.7 -		# we interested in the next line:
     2.8 +		# we are interested in the next line:
     2.9  		#  Type:                              EXEC (Executable file)
    2.10  		# or
    2.11  		#  Type:                              DYN (Shared object file)