SliTaz Repositories

     1.1 --- a/doc/general-questions.md	Sat Feb 02 13:36:54 2019 +0200
     1.2 +++ b/doc/general-questions.md	Sun Feb 03 13:08:25 2019 +0000
     1.3 @@ -3,21 +3,21 @@
     1.4  ## `sed` or patches?
     1.5  
     1.6  Sometimes I come across cases where `sed` is used to change some values in the
     1.7 -source code, or to add / remove / change some parts of the source code.
     1.8 +source code or to add / remove / change some parts of the source code.
     1.9  It may look like a good idea for a one-time job, but you will encounter
    1.10  problems in the future when you upgrade the package.
    1.11  
    1.12 -`sed` works quietly, and it is impossible to understand whether it found what
    1.13 -was needed to be found, whether he replaced what we wanted? Maybe this change
    1.14 -is already in the new sources, and we no longer need `sed` command?
    1.15 +`sed` works quietly and it is impossible to understand whether it found what
    1.16 +was needed to be found, whether it replaced what we wanted? Maybe this change
    1.17 +is already in the new sources and we no longer need `sed` command?
    1.18  
    1.19  If we consider only the updated sources, sometimes it is impossible
    1.20  to understand the essence of the `sed` changes. And then you have to download
    1.21  and analyze the old sources.
    1.22  
    1.23  Feel free to use patches. The `patch` is smart enough to find the necessary
    1.24 -lines in the new sources, and also it will signal to you if your changes have
    1.25 -already been made in the sources, or if the sources has changed so much that
    1.26 +lines in the new sources and also it will signal to you if your changes have
    1.27 +already been made in the sources or if the sources has changed so much that
    1.28  your intervention is required.
    1.29  
    1.30  Go from `sed` to `patch` is easy. You must use the `-o.backup` option (value

     2.1 --- a/modules/compressor	Sat Feb 02 13:36:54 2019 +0200
     2.2 +++ b/modules/compressor	Sun Feb 03 13:08:25 2019 +0000
     2.3 @@ -701,7 +701,7 @@
     2.4  
     2.5  		# 64 bytes is the length of prologue added by awk script (here ~ is $'\n'):
     2.6  		# msgid ""~msgstr ""~"Content-Type: text/plain; charset=UTF-8\n"~~
     2.7 -		# If size is 64 bit then file have no content, we'll remove it with
     2.8 +		# If size is 64 bit then files have no content, we'll remove it with
     2.9  		# all empty uplevel directories.
    2.10  		# For example, look at libbytesize package.
    2.11  		if [ "$(stat -c%s "$tmpfile.awk")" -eq 64 ]; then