From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "Liliana Marie Prikler" <liliana.prikler@gmail.com>,
<56286@debbugs.gnu.org>
Subject: [bug#56286] [PATCH 3/3] gnu: Add pkgconf.
Date: Tue, 28 Jun 2022 20:20:29 +0100 [thread overview]
Message-ID: <CL20EI57NEWA.9KF4S1OONBT4@guix-aspire> (raw)
In-Reply-To: <0d359aa389bbeae5cc6852067c995286e0cc3922.camel@gmail.com>
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?
-- (
next prev parent reply other threads:[~2022-06-28 19:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 17:41 [bug#56286] [PATCHSET] Add pkgconf ( via Guix-patches via
2022-06-28 18:08 ` [bug#56286] [PATCH 1/3] gnu: pkg-config: Qualify import of (guix licenses) ( via Guix-patches via
2022-06-28 18:08 ` [bug#56286] [PATCH 2/3] gnu: pkg-config: Rearrange imports ( via Guix-patches via
2022-06-28 18:08 ` [bug#56286] [PATCH 3/3] gnu: Add pkgconf ( via Guix-patches via
2022-06-28 19:13 ` Liliana Marie Prikler
2022-06-28 19:20 ` ( via Guix-patches via [this message]
2022-06-28 19:45 ` Liliana Marie Prikler
2022-06-28 19:46 ` Liliana Marie Prikler
2022-06-28 20:14 ` ( via Guix-patches via
2022-06-28 20:34 ` [bug#56286] [PATCH v2 1/6] gnu: Add atf ( via Guix-patches via
2022-06-28 20:34 ` [bug#56286] [PATCH v2 2/6] gnu: Add lutok ( via Guix-patches via
2022-06-28 20:34 ` [bug#56286] [PATCH v2 3/6] gnu: Add kyua ( via Guix-patches via
2022-06-28 20:34 ` [bug#56286] [PATCH v2 4/6] gnu: pkg-config: Qualify import of (guix licenses) ( via Guix-patches via
2022-06-28 20:34 ` [bug#56286] [PATCH v2 5/6] gnu: pkg-config: Rearrange imports ( via Guix-patches via
2022-06-28 20:34 ` [bug#56286] [PATCH v2 6/6] gnu: Add pkgconf ( via Guix-patches via
2022-06-28 23:34 ` Maxime Devos
2022-06-29 5:41 ` ( via Guix-patches via
2022-08-03 16:21 ` Efraim Flashner
2023-09-02 3:28 ` Vagrant Cascadian
2024-02-26 16:06 ` bug#56286: Add kyua, lutok, atf Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CL20EI57NEWA.9KF4S1OONBT4@guix-aspire \
--to=guix-patches@gnu.org \
--cc=56286@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=paren@disroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).