Felix Lechner via "Development of GNU Guix and the GNU System
distribution." writes:
> All of it is in the Guix source code, however, which is
> public. I don't have time to look into it for you right now, but I bet
> you and I both would learn a lot!
At least in my case, being able to find thi
Hi Suhail,
On Sun, Oct 06 2024, Suhail Singh wrote:
> It seems this adds it to "native"?
I'm not sure. All of it is in the Guix source code, however, which is
public. I don't have time to look into it for you right now, but I bet
you and I both would learn a lot!
Kind regards
Felix
Hi Felix,
Felix Lechner writes:
>> does use here mean being an "input" to a package?
>
> Yes, precisely. Or being used in a profile.
I see. Thank you.
>> At least for certain variables such as $SSL_CERT_DIR and $SSL_CERT_FILE
>> they only have the desired effect when added to native-search-p
Hi Suhail,
On Sun, Oct 06 2024, Suhail Singh wrote:
> does use here mean being an "input" to a package?
Yes, precisely. Or being used in a profile.
> I would expect ... search-paths or native-search-paths to be ...
> equivalent when not cross compiling. Do you agree?
Not sure. I packages ma
Felix Lechner writes:
>> Does "used" above refer to runtime usage?
>
> It refers to any use of the "python" package.
Since I am trying to understand what constitutes "use", could you please
give examples? For instance does use here mean being an "input" to a
package? Something more/less/else?
Hi Suhail,
On Sat, Oct 05 2024, Suhail Singh wrote:
> Does "used" above refer to runtime usage?
It refers to any use of the "python" package.
The native specifier means that the inputs have the same architecture
that Python is building something else on, rather than the architecture
it building
