tutorial/docs #77

New Issue

ariadne · 2015-06-22T12:12:42Z

techtonik commented

2015-06-22 12:12:42 +00:00

(Migrated from github.com)

I understand that pkgconf if a replacement for some good and old unix tool, but is it possible to host some straight-to-the point tutorial that describes the problem domain for those with no prior experience?

I understand that `pkgconf` if a replacement for some good and old unix tool, but is it possible to host some straight-to-the point tutorial that describes the problem domain for those with no prior experience?

ariadne commented

2015-06-25 13:06:54 +00:00

Would be nice but right now I don't have time to write documentation. If someone else does it, I will merge it.

ariadne commented

2015-06-25 13:11:44 +00:00

In meantime, you could read legacy pkg-config's tutorial: http://people.freedesktop.org/~dbn/pkg-config-guide.html

In meantime, you could read legacy `pkg-config`'s tutorial: http://people.freedesktop.org/~dbn/pkg-config-guide.html

techtonik commented

2015-06-26 05:40:59 +00:00

(Migrated from github.com)

From that page - pkg-config collects metadata about the installed libraries on the system. Is it obligatory to install the libraries? I just
want to point to the location of dependencies in downloadable .zip file, so
that after unpacking I can add its directories to appropriate INCLUDE and
LIB paths.

From that page - `pkg-config collects metadata about the installed libraries on the system`. Is it obligatory to install the libraries? I just want to point to the location of dependencies in downloadable .zip file, so that after unpacking I can add its directories to appropriate INCLUDE and LIB paths.

ariadne commented

2015-06-26 07:17:29 +00:00

Yes, pkg-config is not a package manager in any way. Nor is pkgconf, but a package manager as you describe could be built around it (although this seems like a bad idea)

Yes, `pkg-config` is not a package manager in any way. Nor is `pkgconf`, but a package manager as you describe could be built around it (although this seems like a bad idea)

techtonik commented

2015-06-26 07:33:42 +00:00

(Migrated from github.com)

On Fri, Jun 26, 2015 at 10:17 AM, William Pitcock notifications@github.com
wrote:

Yes, pkg-config is not a package manager in any way. Nor is pkgconf, but
a package manager as you describe could be built around it (although this
seems like a bad idea)

Why it is a bad idea? I need the libraries only for the build process, and
see how much magic is required to set all those paths correctly for the
build -
48cd31a64c/05.wesnoth.py?at=default#cl-419

and imagine how many days I spent trying to figure this out.

On Fri, Jun 26, 2015 at 10:17 AM, William Pitcock notifications@github.com wrote: > Yes, pkg-config is not a package manager in any way. Nor is pkgconf, but > a package manager as you describe could be built around it (although this > seems like a bad idea) Why it is a bad idea? I need the libraries only for the build process, and see how much magic is required to set all those paths correctly for the build - https://bitbucket.org/techtonik/locally/src/48cd31a64c9ec8b198e2b4c9d394d43c45d65bcd/05.wesnoth.py?at=default#cl-419 - and imagine how many days I spent trying to figure this out.

techtonik commented

2015-06-26 07:35:07 +00:00

(Migrated from github.com)

Just to clarify - I don't need package manager. I need a format to describe
the paths to different libraries in the archive.

Just to clarify - I don't need package manager. I need a format to describe the paths to different libraries in the archive.

ariadne commented

2015-06-26 11:03:15 +00:00

As mentioned previously, that's not what pkg-config nor pkgconf do. It's a toolchain tool, what you would probably want to do is have virtual entries in your package database based on .pc files provided. That is what redhat, alpine, etc do. Don't know why Debian hasn't joined that party yet.

As mentioned previously, that's not what `pkg-config` nor `pkgconf` do. It's a toolchain tool, what you would probably want to do is have virtual entries in your package database based on .pc files provided. That is what redhat, alpine, etc do. Don't know why Debian hasn't joined that party yet.

techtonik commented

2015-07-01 07:11:01 +00:00

(Migrated from github.com)

Is pkgconf data format suitable for that purpose? I'd like to avoid writing the stuff from scratch if possible.