On 25-09-2023 22:35, Simon Tournier wrote:
Hi,
On Mon, 25 Sep 2023 at 14:13, MSavoritias wrote:
So saying that the people who don't know guile or guix need to first
contribute docs is pretty ridiculous.
Why? Could you explain more why it appears to you “ridiculous”?
My frustration seems
2023-09-25 21:53 mek...@posteo.de:
Putting all three thoughts together, I'd gather this code
suggestion:
[2. application/emacs-lisp; new.el]...
Sorry, it seems I forgot to apply my first thought in the appended
file... (setq bug-reference-url-format
"https://issues.guix.gnu.org/%s";). Sorr
* mumi/web/graphql.scm (): Include merged_with.
---
mumi/web/graphql.scm | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/mumi/web/graphql.scm b/mumi/web/graphql.scm
index 6dcb8ce..2c7c676 100644
--- a/mumi/web/graphql.scm
+++ b/mumi/web/graphql.scm
@@ -69,7 +69,17
> > When will the above website be updated to use the latest manual
> > information about branches?
>
>
> What do you mean?
>
> 1. The manual you are pointing is the released v1.4.0 manual, not the
> latest one. This v1.4.0 manual is set in stone and is a snapshot
> of Guix at v1.4.0.
if Guix
Hi,
On Tue, 26 Sept 2023 at 11:55, Attila Lendvai wrote:
> > > When will the above website be updated to use the latest manual
> > > information about branches?
> >
> > What do you mean?
> >
> > 1. The manual you are pointing is the released v1.4.0 manual, not the
> > latest one. This v1.4.0 manu
Hi Simon and Attila,
I like the idea of releasing the website as a rolling release.
The issue with keeping the release manual around is in edge cases like these
where even though we have an old release manual and a rolling release manual,
people contributing are expected to follow the latest pr
On 9/24/23 1:27 AM, Andy Tai wrote:
Hi, curious if core-updates still a thing?There seems a branch by
that name and the manual still says patches causing large number of
rebuilds should go to core-updates, at least for these not aiming at a
specific feature branch.
I have the same question.
Hi Andy,
Andy Tai writes:
> Hi, curious if core-updates still a thing?There seems a branch by
> that name and the manual still says patches causing large number of
> rebuilds should go to core-updates, at least for these not aiming at a
> specific feature branch.
It is. We can't have topic
Hi Katherine,
Katherine Cox-Buday writes:
> On 9/24/23 1:27 AM, Andy Tai wrote:
>> Hi, curious if core-updates still a thing?There seems a branch by
>> that name and the manual still says patches causing large number of
>> rebuilds should go to core-updates, at least for these not aiming at
Hi,
Simon Tournier writes:
> Hi,
>
> On Tue, 26 Sept 2023 at 11:55, Attila Lendvai wrote:
>> > > When will the above website be updated to use the latest manual
>> > > information about branches?
>> >
>> > What do you mean?
>> >
>> > 1. The manual you are pointing is the released v1.4.0 manual,
> > My expectation for browsing help from a website these days is that ...
I concur!
On Tue, 26 Sept 2023 at 11:55, Attila Lendvai
wrote:
if Guix is using a rolling release model, then maybe it's not an
unreasonable expectation that the online manual also follows the
latest in the git repo, no?
maybe we should stop prefixing devel/, and start prefixing the
releases?
W
Hi all,
I've been thinking on a plan to address this old NFS question.
The plan:
1. Allow the file-system `dependencies' field to accept arbitrary
shepherd symbols as well.
This can be done by having the `dependency->shepherd-service-name'
in (gnu services base) also accept matching against a
Hi Bruno,
Am Dienstag, dem 26.09.2023 um 19:35 +0100 schrieb Bruno Victal:
> Hi all,
>
> I've been thinking on a plan to address this old NFS question.
>
> The plan:
>
> 1. Allow the file-system `dependencies' field to accept arbitrary
> shepherd symbols as well.
Sure, why not?
> This can be
Hi,
On Tue, Sep 26 2023, Peter Polidoro wrote:
> Web searches for "guix manual" do not tend to show the devel
> version so it can be difficult for new users to find
This entire discussion, and especially Attila's excellent
tongue-in-cheek point, probably belongs into Bug#51000. [1]
Personally,
Ekaitz Zarraga writes:
An option is to make some kind of user-story based documentation
might help?
As a long-time wannabe-contributor who has been intimidated by the
unfamiliar process, I agree with this statement.
In fact, (to acknowledge the other more controversial branch of
this co
Hi there,
I'm trying to package Incudine, a Music/DSP programming environment for
Common Lisp. I'm stuck with the binding of libsndfile. First
libsndfile.so could not be found, but I fixed the paths like it is
commonly done in other CL packages. Next problem is that somehow the
bindings are not wo
17 matches
Mail list logo
