Hi!
Ricardo Wurmus skribis:
> Philip McGrath writes:
>
>> As a Racketeer, I think you're half way to reinventing contracts.
>
> Yes, I was in fact thinking of contracts, but shied away from mentioning
> them :) The reason is that I think we can cover a lot of distance with
> just a few simple
Ricardo Wurmus skribis:
> Maxim Cournoyer writes:
>
>> I hear we now have "field sanitizers" on Guix records; without having
>> dug the details, it seems to be we could add a predicate validating the
>> input there?
>
> I don’t see how that would help here. In my example the service values
> th
Hello!
Vagrant Cascadian skribis:
> On 2022-02-19, m...@excalamus.com wrote:
>> On Sat, 19 Feb 2022 21:33:47 -0500 Vagrant Cascadian
>> wrote
>> > Every now and then someone stumbles into #guix and ask questions that
>> > I've gleaned over time are off-topic (e.g. non-free softwar
Hi,
Christopher Baines skribis:
> I think I figured out that it's related to grafts. I've attached a test
> script which computes the channel instance derivation for mips64el-linux
> which I'm not set up to build things for (if you can build for
> mips64el-linux, replace this with a system you c
Hi,
Maxime Devos skribis:
> 2. Instead of building all of Guix as a single derivation,
> create a DAG of derivations. More concretely:
>
> First read the *.scm files to determine which module imports
> which modules. Then to compile, say, (gnu packages acl),
> a derivation
Hello,
Chris Marusich skribis:
> The Guix manual recommends running nscd:
>
> https://guix.gnu.org/manual/en/html_node/Application-Setup.html
>
> However, Fedora intends to remove it:
>
> https://fedoraproject.org/wiki/Changes/RemoveNSCD
D’oh! This is bad. It might suggest that nscd will vani
Hello,
Stefan Karrmann skribis:
> My hard binay seed is a monitor, which takes octal encoded octets (aka
> bytes) as input, writes the octets in reverse order into the memory, and
> finally jumps to the new code. It's size is:
>
> - for octal keyboard input on x86: 32 octets (!)
>
Hello,
Ludovic Courtès writes:
> Ricardo Wurmus skribis:
>
>> Maxim Cournoyer writes:
>>
>>> I hear we now have "field sanitizers" on Guix records; without having
>>> dug the details, it seems to be we could add a predicate validating the
>>> input there?
>>
>> I don’t see how that would help
Hi,
On Monday, February 28, 2022 7:59:02 AM EST Ludovic Courtès wrote:
> Hi!
>
> Ricardo Wurmus skribis:
> > Philip McGrath writes:
> >> As a Racketeer, I think you're half way to reinventing contracts.
> >
> > Yes, I was in fact thinking of contracts, but shied away from mentioning
> > them :
When creating a profile containing both clang-toolchain and gcc-toolchain I
see the same issue as in #43023; however, if I specify the default
gcc-toolchain (currently gcc-toolchain@10) then clang and gcc work just
fine together.
--8<---cut here---start->8---
$
tumashu schreef op ma 28-02-2022 om 08:22 [+0800]:
> by the way, if my system-config enable mate-1.24 desktop type. when I
> install a different version mate in
> my home, for example 1.26, which one will be use when I enter my deskop by
> slim?
I don't know. I'm currently on a foreign syste
Ludovic Courtès schreef op ma 28-02-2022 om 14:17 [+0100]:
> Hi,
>
> Maxime Devos skribis:
>
> > 2. Instead of building all of Guix as a single derivation,
> > create a DAG of derivations. More concretely:
> >
> > First read the *.scm files to determine which module imports
> >
Hi Christine & co.,
This will be my last mail on this topic. It's addressed to everyone.
Thank you for putting so much time into your response. I'm responding
late because I had too much anxiety to open my mail client, and it looks
like my gut feeling was not wrong.
I'm sad to say that I have
Hello Ludo,
Apologies for the late reply, but for some unknown reason this message was
in my spams.
I agree with the proposed licensing terms!
I hope everything is going well with Guix. I will graduate this year, so I
look forward to being more active during the summer as I really enjoyed my
Out
Just to keep it clear, Taylan,
You didn't in any case listen to what I actually said which
was that you are forcing us to have this debate. You don't
care if we want or we don't.
I don't want to have this discussion and you are still
pushing.
I never said you were wrong or not, just wanted you t
Taylan,
You asked me to take the time to explain the hurt you caused, and I did.
I spent a whole day on it. It was not easy. In response you provided a
long justification backing up the very thing you were asked not to do,
the very thing identified as causing this much hurt.
But you've made it,
Taylan,
You have been asked repeatedly to stop and yet, you just reiterated what
we know has already proven to be hurtful. That’s enough.
Some things are indeed not up for debate, and the spirit of the code of
conduct is one of them. As I return from vacation, I see that long
thread that immedi
Hi,
Ludovic Courtès writes:
> Taylan,
>
> You have been asked repeatedly to stop and yet, you just reiterated what
> we know has already proven to be hurtful. That’s enough.
I agree. Let's put an end to this and related threads that don't
further our project in any positive way. The Guix mai
Good god, man.
You spectacularly botched your original proposal. That should have been the
end of it. Instead, we all have to suffer through your inability not to have
the last word. Or indeed thousand words. That's cruel & unusual collective
punishment, that is.
To protect you from furthe
19 matches
Mail list logo
