Github messages for voidlinux
 help / color / mirror / Atom feed
From: newbluemoon <newbluemoon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: $XBPS_CROSS_BASE leaking into pkgconfig
Date: Wed, 20 May 2020 07:06:29 +0200	[thread overview]
Message-ID: <20200520050629.g3cxY42BQ3idFECEhcjlWIwa9sO_qkB5acWnq24jPjA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22139@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 515 bytes --]

New comment by newbluemoon on void-packages repository

https://github.com/void-linux/void-packages/issues/22139#issuecomment-631238976

Comment:
Perhaps a combination? A hook to fix the `.pc` files automatically and after that a `grep` run for finding leftovers that require manual action? I agree that a hook alone for everything might not be a good idea, e.g. it probably breaks cross-compiler packages, but using it on pkgconfig might save some work and is often the only place where the cross base leaks into.

  parent reply	other threads:[~2020-05-20  5:06 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 17:10 [ISSUE] " newbluemoon
2020-05-19 22:46 ` sgn
2020-05-19 22:48 ` sgn
2020-05-20  0:45 ` sgn
2020-05-20  5:06 ` newbluemoon [this message]
2020-05-20  5:33 ` newbluemoon
2020-05-20 14:18 ` sgn
2020-05-20 14:32 ` newbluemoon
2020-05-20 20:23 ` newbluemoon
2020-05-21 12:29 ` sgn
2020-05-21 12:31 ` sgn
2020-05-22  5:32 ` sgn
2020-05-22  5:34 ` sgn
2020-05-22  5:34 ` sgn
2020-05-22  5:34 ` sgn
2020-05-22  5:35 ` sgn
2020-05-22  5:35 ` sgn
2020-05-22  5:36 ` sgn
2020-05-22  5:54 ` sgn
2020-05-22  7:49 ` sgn
2020-05-31  6:13 ` sgn
2020-05-31  6:13 ` sgn
2020-05-31  6:13 ` sgn
2020-05-31  6:14 ` sgn
2020-05-31  6:15 ` sgn
2020-05-31  6:16 ` sgn
2020-05-31  6:16 ` sgn
2020-05-31  6:19 ` sgn
2020-05-31  6:20 ` sgn
2021-01-01 14:20 ` sgn
2022-04-16  2:02 ` github-actions
2022-04-30  2:13 ` [ISSUE] [CLOSED] " github-actions

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200520050629.g3cxY42BQ3idFECEhcjlWIwa9sO_qkB5acWnq24jPjA@z \
    --to=newbluemoon@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).