unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: "(" <paren@disroot.org>, 56286@debbugs.gnu.org
Subject: [bug#56286] [PATCH 3/3] gnu: Add pkgconf.
Date: Tue, 28 Jun 2022 21:46:43 +0200	[thread overview]
Message-ID: <3840bb9e97d7ecf608714647eff1d83df6db5391.camel@gmail.com> (raw)
In-Reply-To: <4e2b6ef0e27ca5b3fa964d2f74a92a362e672e4c.camel@gmail.com>

Am Dienstag, dem 28.06.2022 um 21:45 +0200 schrieb Liliana Marie
Prikler:
> I mean as a Scheme variable, rather than typing it out twice.  It's
> not the biggest priority right now, but if another pkg-config
> implementation rolls around, we might want to consider
> $PKG_CONFIG_PATH a "standard" search-path.
Following up to that, I think I am slightly annoyed by typing out the
same thing twice.  You could use (package-native-search-paths pkg-
config) instead, especially since they're in the same module and all.

Cheers




  reply	other threads:[~2022-06-28 19:47 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
2022-06-28 19:45         ` Liliana Marie Prikler
2022-06-28 19:46           ` Liliana Marie Prikler [this message]
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=3840bb9e97d7ecf608714647eff1d83df6db5391.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=56286@debbugs.gnu.org \
    --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).