From: Ionen Wolkens <ionen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] profiles/default/linux: export cache variables for sed and friends
Date: Tue, 10 Dec 2024 03:57:02 -0500 [thread overview]
Message-ID: <Z1gCXtiC_PFzlnjY@eversor> (raw)
In-Reply-To: <df0ca4dd-cd14-46fb-9bec-705691e8860a@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
On Tue, Dec 10, 2024 at 03:26:38AM -0500, Eli Schwartz wrote:
> On 12/10/24 3:02 AM, Ionen Wolkens wrote:
> > Albeit I don't understand what would be doing in there, setting the
> > full path for the current profile wouldn't accomplish anything for
> > binpkg-on-different-usr-type-profile.
>
>
> It surely would -- the point of setting it for the current profile is to
> make ./configure stop storing overly-specific build time paths, which
> means that the resulting binpkg is now well-formed and works on both
> profiles.
I said *full* path. I was trying to figure out the reasoning of using
profile.bashrc vs just doing ="sed" without a path in profile itself,
and guessing what may have wanted to do there (like a conditional
to set a different path, or read EPREFIX.. but that just replicate
what ./configure will figure out itself).
--
ionen
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-12-10 8:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 22:55 [gentoo-dev] [PATCH] profiles/default/linux: export cache variables for sed and friends Sam James
2024-12-06 0:44 ` Michael Orlitzky
2024-12-10 5:46 ` Sam James
2024-12-10 8:02 ` Ionen Wolkens
2024-12-10 8:13 ` Sam James
2024-12-10 8:26 ` Eli Schwartz
2024-12-10 8:57 ` Ionen Wolkens [this message]
2024-12-10 9:22 ` Ionen Wolkens
2024-12-10 5:54 ` Eli Schwartz
2024-12-10 18:31 ` Michael Orlitzky
2024-12-10 19:33 ` Eli Schwartz
2024-12-10 22:03 ` Michael Orlitzky
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=Z1gCXtiC_PFzlnjY@eversor \
--to=ionen@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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