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
signature.asc
Description: PGP signature
