[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#56286] [PATCH 3/3] gnu: Add pkgconf.
From: |
( |
Subject: |
[bug#56286] [PATCH 3/3] gnu: Add pkgconf. |
Date: |
Tue, 28 Jun 2022 20:20:29 +0100 |
On Tue Jun 28, 2022 at 8:13 PM BST, Liliana Marie Prikler wrote:
> I think this is a misinterpretation on your part or a confusing wording
> on theirs. Basically, pkgconf does not *link* against any "huge"
> binary, so it's fine. Never mind that glib is a sane dependency to
> have or that it also complains about pkg-config's license, which is
> most meaningless in the context of tools you invoke at build time.
You make an excellent point there. I'll add the guixrus kyua package and
its dependencies in a moment. Hopefully your note about using check
after install will work. Is there an easy way to switch them around?
> > + (list #:tests? #f))
> > + (native-inputs (list ;; pkgconf's autotools setup forbids the
> > use of any
> > + ;; earlier version of autoconf than 2.71.
> > + autoconf-2.71
> > + automake
> > + libtool))
> > + (native-search-paths
> > + (list (search-path-specification
> > + (variable "PKG_CONFIG_PATH")
> > + (files '("lib/pkgconfig" "lib64/pkgconfig"
> > "share/pkgconfig")))))
> I'm not sure if we want to provide $PKG_CONFIG_PATH as a variable, but
> there's at least two definitions within the same file now :)
What alternative would there be to providing $PKG_CONFIG_PATH as a
variable?
-- (
[bug#56286] [PATCH 2/3] gnu: pkg-config: Rearrange imports., (, 2022/06/28
[bug#56286] [PATCH v2 1/6] gnu: Add atf., (, 2022/06/28
- [bug#56286] [PATCH v2 3/6] gnu: Add kyua., (, 2022/06/28
- [bug#56286] [PATCH v2 5/6] gnu: pkg-config: Rearrange imports., (, 2022/06/28
- [bug#56286] [PATCH v2 2/6] gnu: Add lutok., (, 2022/06/28
- [bug#56286] [PATCH v2 4/6] gnu: pkg-config: Qualify import of (guix licenses)., (, 2022/06/28
- [bug#56286] [PATCH v2 6/6] gnu: Add pkgconf., (, 2022/06/28