From 609524fe70681a6cf689629fb5f16837688e6c3d Mon Sep 17 00:00:00 2001 From: olf Date: Thu, 7 Oct 2021 04:17:35 +0200 Subject: [PATCH 1/2] [README.md] Soften and clarify wording --- README.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 5a41cae..66a1b93 100644 --- a/README.md +++ b/README.md @@ -71,16 +71,15 @@ do let us know, but also make sure that the .pc files are valid and follow the r the [pkg-config tutorial][fd-tut], as most likely fixing them to follow the specified rules will solve the problem. -Additionally, **we do not consider pkgconf doing what you tell it to do, when pkg-config +Additionally, **we do not consider pkgconf doing what you tell it to do, in cases for which pkg-config fails to do so, to be a bug**. If, for example, you use environment variables such as `PKG_CONFIG_SYSTEM_[INCLUDE|LIBRARY]_PATH` and then find yourself surprised that `pkgconf` is stripping `-I` and `-L` flags relating -to those paths, it's not a `pkgconf` problem -- `pkgconf` is doing exactly what you told +to those paths, it is not a `pkgconf` problem -- `pkgconf` is doing exactly what you told it to do. -We will reject bugs like this, and if you choose to violate our [Code of Conduct](CODE_OF_CONDUCT.md) -by demanding we fix your non-bug, we will fix the problem by banning you from the repo instead. +We will reject bugs like this, and if someone insists on fixing such a non-bug, this constitutes a violation of our [Code of Conduct](CODE_OF_CONDUCT.md), which may be addressed by banning from this repository. ## compiling `pkgconf` and `libpkgconf` on UNIX -- 2.41.0 From 1f76c91fcd575adb372d3cbb06d92d6ae5605d18 Mon Sep 17 00:00:00 2001 From: olf Date: Thu, 7 Oct 2021 04:26:33 +0200 Subject: [PATCH 2/2] [README.md] Roughly make line lenghts consistent --- README.md | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 66a1b93..1570aea 100644 --- a/README.md +++ b/README.md @@ -3,9 +3,9 @@ `pkgconf` is a program which helps to configure compiler and linker flags for development libraries. It is similar to pkg-config from freedesktop.org. -`libpkgconf` is a library which provides access to most of `pkgconf`'s functionality, to allow -other tooling such as compilers and IDEs to discover and use libraries configured by -pkgconf. +`libpkgconf` is a library which provides access to most of `pkgconf`'s functionality, +to allow other tooling such as compilers and IDEs to discover and use libraries +configured by pkgconf. ## using `pkgconf` with autotools @@ -71,15 +71,17 @@ do let us know, but also make sure that the .pc files are valid and follow the r the [pkg-config tutorial][fd-tut], as most likely fixing them to follow the specified rules will solve the problem. -Additionally, **we do not consider pkgconf doing what you tell it to do, in cases for which pkg-config -fails to do so, to be a bug**. +Additionally, **we do not consider pkgconf doing what you tell it to do, in cases for +which pkg-config fails to do so, to be a bug**. If, for example, you use environment variables such as `PKG_CONFIG_SYSTEM_[INCLUDE|LIBRARY]_PATH` and then find yourself surprised that `pkgconf` is stripping `-I` and `-L` flags relating to those paths, it is not a `pkgconf` problem -- `pkgconf` is doing exactly what you told it to do. -We will reject bugs like this, and if someone insists on fixing such a non-bug, this constitutes a violation of our [Code of Conduct](CODE_OF_CONDUCT.md), which may be addressed by banning from this repository. +We will reject bugs like this, and if someone insists on fixing such a non-bug, this +constitutes a violation of our [Code of Conduct](CODE_OF_CONDUCT.md), which may be +addressed by banning from this repository. ## compiling `pkgconf` and `libpkgconf` on UNIX @@ -105,8 +107,8 @@ flags like so: ## compiling `pkgconf` and `libpkgconf` with CMake (usually for Windows) pkgconf is compiled using CMake on Windows. In theory, you could also use CMake to build -on UNIX, but this is not recommended at this time as it pkgconf is typically built much earlier -than CMake. +on UNIX, but this is not recommended at this time as it pkgconf is typically built much +earlier than CMake. $ mkdir build $ cd build -- 2.41.0