Am Donnerstag, dem 14.09.2023 um 15:51 -0700 schrieb Vagrant Cascadian:
> On 2023-09-10, Liliana Marie Prikler wrote:
> > Am Donnerstag, dem 07.09.2023 um 09:12 -0700 schrieb Vagrant
> > Cascadian:
> > > I am much more comfortable with the "Fixes" convention of:
> > >
> > > Fixes: https://issues
2023-09-13 16:36 m...@cbaines.net:
I think this has been talked about for a while [1], but I want
to make it happen. Currently the guix-daemon is still similar to
the nix-daemon that it was forked from, and is implemented in
C++. I think that a Guile implementation of the guix-daemon will
sim
On 2023-09-10, Liliana Marie Prikler wrote:
> Am Donnerstag, dem 07.09.2023 um 09:12 -0700 schrieb Vagrant Cascadian:
>> I am much more comfortable with the "Fixes" convention of:
>>
>> Fixes: https://issues.guix.gnu.org/NNN
> I like the idea, but we should also consider the bugs.gnu.org address
Hi Simon, Saku
Thank you for your answers.
First, I should have slept on my email instead of sending it right away.
I was still dealing with the frustration of having made a fool of myself
with debbugs, which compounded with wrestling earlier with golang build
system. My tone was unnecessarily ha
Hello,
Le 14 septembre 2023 12:30:41 GMT-04:00, Vagrant Cascadian
a écrit :
[…]
>> I doubt the Change-Id idea would help much closing *bugs* on the
>> bug-guix tracker, but I'd expect it to be useful to close already merged
>> (but forgotten on the guix-patches tracker) *patches*.
>
>Well, all
I think that quite a few Guix users end up not committing to Guix because
of how daunting and strange the process seems.
In particular, having an alternate, easy-to-use interface for updating
package definitions specifically could be very useful.
The greatest strength of Guix is that it can be ver
Hi Edouard,
It is very important to speak up, although that makes me sad to read
such poor feedback experience.
Well, the friction is about Debbugs. Maybe I repeat myself: Debbugs is
initially thought to be a bug tracker system and not a patch track system.
Do not take me wrong, I am not trying
Hi,
On Thu, 14 Sept 2023 at 18:51, Ludovic Courtès wrote:
> For the record, that’s a 6% increase:
>
> --8<---cut here---start->8---
> $ guix size guix | tail -1
> total: 633.0 MiB
> $ guix size guix git-minimal | tail -1
> total: 675.7 MiB
> --8<--
Am Donnerstag, dem 14.09.2023 um 11:42 +0200 schrieb Giovanni Biscuolo:
> OK! :-) Let's see how this relates to the 2 use cases we are talking
> about:
>
> 1. Use "Fixes:" (et al) in commit msg to tell "the hook" to close the
> bug.
>
> This "action" implies that the commit we are pushing upstre
Hi!
Maxim Cournoyer skribis:
> So given there's no technical reasons not to use libgit2, I'd use that
> and keep the closure size down.
For the record, that’s a 6% increase:
--8<---cut here---start->8---
$ guix size guix | tail -1
total: 633.0 MiB
$ guix siz
Hi Ludo,
On Thu, 14 Sep 2023 at 12:30, Ludovic Courtès wrote:
>but I don’t think
> we can get a decent throughput if we shell out for all these things
> (assuming ‘git’ can even give us raw data).
Do you consider that Magit does not have a
Hi,
On Thu, 14 Sep 2023 at 12:27, Giovanni Biscuolo wrote:
> Please can you expand what troubles do you see in automatically adding
> 'Change-Id:' using a hook-commit-msg like
> https://gerrit-review.googlesource.com/Documentation/cmd-hook-commit-msg.html
> ?
1. The hook must be installed.
2. T
Christopher Baines skribis:
> I'm not very familiar with actors, but I guess that's similar to having
> a bunch of cooperating fibers which handle different things.
Yes. Specifically, actors here are a fiber together with a channel;
each actor looks like:
(let loop ((state …))
(match (ge
On 2023-09-13, Maxim Cournoyer wrote:
> Vagrant Cascadian writes:
>> On 2023-09-09, Maxim Cournoyer wrote:
>>> The Change-Id stays the same unless you manually edit it out of your
>>> commit message when amending / rebasing, so the commit hash may change
>>> while the Change-Id stays the same. So
(Warning: this email is in french because the meeting is supposed
to be held in French… and in person.)
Bonjour Guix,
Ce jeudi 28 septembre à 19h, se tiendra la première édition de Guix@Paris
ouverte au public.
## Programme
Il n'y a pas vraiment de programme. Le but est que les utilisat·rice·e
Ludovic Courtès writes:
>> Rewrites are risky because you only get the value right at the end,
>> therefore the priority is to get a minimal but viable implementation in
>> Guile that can be switched to, and not to get distracted on adding or
>> improving functionality unnecessarily. That is bet
On Thu, Sep 14, 2023 at 11:31 AM Ludovic Courtès wrote:
>
> Hi!
>
> "Thompson, David" skribis:
>
> > I'm curious to hear more about your inter-process transport needs!
>
> I’d like to have actors running in separate processes on the same
> machine. I wouldn’t want them to communicate over Tor or
Hi Greg,
(It’s been two months but I completely missed this message.)
Greg Hogan skribis:
> On Wed, Mar 8, 2023 at 7:03 AM Ludovic Courtès wrote:
>>
>> Hello,
>>
>> This change makes things like:
>>
>> guix build --with-input=guile=guile-next guix -n --no-grafts
>>
>> more useful and tractab
Christopher Baines skribis:
> I think compatibility is a priority, and although I haven't looked too
> much in to the details yet, I think it's quite realistic.
>
> I think it's very important for Guix to keep compatibility with older
> daemons, and on the daemon side, I'd want to see the Guile
>
Simon Tournier skribis:
> IIUC, the current two “builder” backend are:
>
> + local ’guix-daemon’: the queue of derivations is processed using one
>strategy – the one implemented in C++,
>
> + ’cuirass remote-server’: the queue of derivations is processed using
>another strategy – implem
Hi!
"Thompson, David" skribis:
> I'm curious to hear more about your inter-process transport needs!
I’d like to have actors running in separate processes on the same
machine. I wouldn’t want them to communicate over Tor or TCP+TLS;
rather, I’d like them to use AF_UNIX sockets, “abstract socket
Hi Christopher,
Christopher Baines skribis:
> My plan is to focus on this over the next year. I left my previous day
> job quite a few months ago now to take a bit of a break, that's the main
> reason I've been able to spend more time trying to push forward some of
> the QA stuff. With some mone
Hi Chris,
Christopher Baines writes:
> Hey!
>
> I think this has been talked about for a while [1], but I want to make it
> happen. Currently the guix-daemon is still similar to the nix-daemon
> that it was forked from, and is implemented in C++. I think that a Guile
> implementation of the guix
Hey Ludo,
On Wed, Sep 13, 2023 at 5:08 PM Ludovic Courtès wrote:
>
> With this actor split, one could implement another “builder” backend,
> for instance one that talks to a Build Coordinator process. It’s also
> obviously close to the programming model encouraged by Goblins, which
> should make
Hi Cayetano! Allow me to chime in, although I'm
green.
Cayetano Santos
aliandika:
> Hi Guix,
>
> Following a recent patch to an snapshot of an emacs package
> (emacs-mastodon), where latest stable (tagged) release dates back from
> a long time, the question of whether to send patches for
Maxim Cournoyer writes:
[...]
> I like the 'Closes: ' trailer idea; it's simple. However, it'd need to
> be something added locally, either the user typing it out (unlikely for
> most contributors) or via some mumi wizardry (it's unlikely that all
> users will use mumi), which means its usage (
Simon Tournier skribis:
> On my machine, I get something less spectacular for a history with 1000
> commits in between.
>
> scheme@(guix-user)> ,time (commit-relation* 1000th newest)
> $1 = ancestor
> ;; 0.128948s real time, 0.082921s run time. 0.046578s spent in GC.
> scheme@(guix-user)> ,time
Simon Tournier writes:
[...]
>> maybe ChangeIds really trump the explicit tags proposed by Giovanni
>> or myself here. Whether that justifies the cognitive overhead of
>> juggling them around on every submission remains to be shown or
>> disproven.
>
> I agree. I am not convinced by the benef
Hi Liliana
Liliana Marie Prikler writes:
> Am Mittwoch, dem 13.09.2023 um 11:27 -0400 schrieb Maxim Cournoyer:
[...]
> I do wonder how the ChangeId would work in practice.
It's a «tag to track commits across cherry-picks and rebases.»
It is used by Gerrit to identify commits that belong to t
Hi,
Josselin Poiret skribis:
> My opinion is that the preferred API for Git is still the UNIX one via
> plumbing commands. Anything else is trying to catch up to it, and then
> we get into this conundrum that we want to do everything in Scheme, but
> we're unable to do it as well as Git itself.
Hello!
Josselin Poiret skribis:
> After looking a bit more into guix pull speed, or to be more precise the
> "Computing Guix derivation..." step, which is not substitutable. I've
> come to the conclusion that the thing that takes the majority of the
> time is loading the files that define the p
Hi Maxim and Vagrant,
I'm sorry for some of the inconprehensions.
Finally I think we got a useful design overall for the _two_ user cases
and the related pieces of metadata and algorithms, now it's time for
_two_ implementations proposals, that also means _code_...
If nihil obstat, I'm going to
Hi,
Distopico skribis:
> Is it possible to define/express CLI options from manifest.scm or
> guix.scm? For example, I have
>
> ```
> guix shell \
> -m manifest.scm \
> --container -F -N -P \
> --share=/opt/android-sdk \
> --share=$HOME/.android/avd \
> --share=$HOME/.gra
> Dear Guix,
>
> I've just blown up Guix's debbugs by opening (and then closing) 33 bugs
> instead of sending a 33-commits patch series.
>
> I've also seen that there is a huge discussion on the cognitive overhead
> of contributing. I will read it as soon as I can spare more time on this.
>
> I
Simon Tournier writes:
>> Of course the Swineherd is also available as a Guix package called
>> “swineherd”.
>
> Hum, I did (or adding guile):
>
> guix time-machine -q -- shell swineherd
>
> Then I do not know what to do. What are the basic steps for testing it?
There are no executables.
Vagrant Cascadian writes:
> On 2023-09-13, Christopher Baines wrote:
>> I think this has been talked about for a while [1], but I want to make it
>> happen. Currently the guix-daemon is still similar to the nix-daemon
>> that it was forked from, and is implemented in C++. I think that a Guile
>>
Dear Guix,
I've just blown up Guix's debbugs by opening (and then closing) 33 bugs
instead of sending a 33-commits patch series.
I've also seen that there is a huge discussion on the cognitive overhead
of contributing. I will read it as soon as I can spare more time on this.
I find git email's w
Maxim Cournoyer writes:
>> The transformation toward a Guile daemon is a point of consistency and
>> pride for the project and therefore unlikely to be second-guessed or
>> reverted. My recommendation is to replace the daemon gradually—working
>> from (apply system* (command-line) downward—and m
Fannys writes:
>> But again, even if this is a great option for you, it might be a really bad
>> option for some other people. Everybody does not have the time to spend
>> learning emacs, or other specific tool. It's ok if the workflow suggests that
>> but it's not great if we have no other alt
MSavoritias writes:
> Simon Tournier writes:
>
>> Hi,
>>
>> On Tue, 29 Aug 2023 at 12:53, MSavoritias wrote:
>>
>>> Do you know if there are any plans to write a scheme bug/patching
>>> system? Because looking a bit into it, it doesn't seem like its that
>>> actively developed so maybe we wou
Hi,
On Thu, 14 Sept 2023 at 08:53, Giovanni Biscuolo wrote:
> To remain /in topic/: I think that adopting a «web based PR model» will
> definitely _not_ decrease the cognitive overhead for contributors.
What could potentially decrease the cognitive overhead for
contributors when using a "web ba
Hello,
Am Wed, Sep 13, 2023 at 09:14:52PM +0200 schrieb Liliana Marie Prikler:
> I do wonder how the ChangeId would work in practice. Since it's not
> really assigned by the committer, it would have to be generated "on the
> fly" and attached to the mail in between, which could result in all
> ki
Hi,
Really cool! Congrats Chris! :-)
On Wed, 13 Sep 2023 at 13:13, Maxim Cournoyer wrote:
> I had some musing about the daemon recently; I was thinking libguile
> could be added to our old C++ daemon, which could then replace its
> functions piece-wise with Scheme implemented ones?
Maxim, you
Hi,
It is really cool! :-)
On Wed, 13 Sep 2023 at 23:08, Ludovic Courtès wrote:
> - The "builder" spawns derivation builds. There are currently two
> implementations: the local builder sends build requests to the local
> 'guix-daemon' process, while the remote build delegates builds
44 matches
Mail list logo
