The docs contain this recommended Emacs setting:
@lisp
;; @r{Assuming the Guix checkout is in ~/src/guix.}
(with-eval-after-load 'geiser-guile
(add-to-list 'geiser-guile-load-path "~/src/guix"))
@end lisp
I haven't been using it for a while because I remember it causing
trouble whenever I was
On 8/20/23 19:35, B. Wilson wrote:
> Hello Guix,
>
> Knee deep in CMake hell here and would appreciate a helping hand. ArrayFire
> build is defeating me:
>
> CMake Error at
> /gnu/store/ygab8v4ci9iklaykapq52bfsshpvi8pw-cmake-minimal-3.24.2/share/cmake-3.24/Modules/ExternalProject.cmake:3269
On 8/24/23 12:53 PM, Simon Tournier wrote:
Hi,
At some point, I sympathize.
On Wed, 23 Aug 2023 at 10:25, Katherine Cox-Buday
wrote:
I don't use the email-based patch workflow day-to-day, so this is
another area where I spend a lot of time trying to make sure I'm doing
things correctly.
Hi Maxim,
On Sun, Jul 30, 2023 at 09:50 PM, Maxim Cournoyer wrote:
> Hi John,
>
> John Kehayias writes:
>
> [...]
>
>> I'll open a branch merge request issue later today as per new
>> procedure for QA. Though I believe that only builds 2 branches, which
>> is occupied at the moment. Or can
On 8/24/23 12:33 AM, ( wrote:
* We could support a managed web-based workflow
The problem with this is that it would not be possible without changing
the git hosting entirely to something like Gitea. I'm personally a fan
of the email-based workflow; what, specifically, is it that bothers you
Hi Katherine,
On Wed, Aug 23, 2023 at 10:12 AM, Katherine Cox-Buday wrote:
> On 8/22/23 8:24 AM, Felix Lechner via Development of GNU Guix and the
> GNU System distribution. wrote:
>> Hi Attila,
>>
>> On Tue, Aug 22, 2023 at 6:14 AM Attila Lendvai wrote:
>>>
>>> currently the go build system in
On 8/23/23 9:33 PM, Ahmed Khanzada via Development of GNU Guix and the
GNU System distribution. wrote:
My wife and I are currently trying, so I hope to be a busy parent soon too!
Good luck to you!
The debate comes down to: the people contributing the most code already
have a very familiar
On 8/24/23 6:10 PM, Ekaitz Zarraga wrote:
Lots of important use cases that
Guix could serve are ignored because the people who need them are not
represented in our community and/or they can't contribute and no one is
able/willing to write code for them.
On 8/23/23 6:18 PM, Csepp wrote:
* Contributing to Guix is not for you
I would be really sad if someone ever said this, but I guess it's a
possibility. Maybe someone like me just can't be a contributor to
Guix until
I have the bandwidth to manage all the details. I would
On 8/25/23 3:57 AM, Attila Lendvai wrote:
Otherwise I do not get your point: I keep untreated messages with the latest
patch version in my Guix inbox, and file away the others in a separate mbox.
So things are not flat, but have two levels: "to be treated" or "done".
my point is that in a PR
On 8/23/23 12:03 PM, Andreas Enge wrote:
Hello,
Am Wed, Aug 23, 2023 at 10:27:31AM -0700 schrieb Felix Lechner via Development
of GNU Guix and the GNU System distribution.:
I can't ever seem to get the GNU style commit messages correct.
Neither can I. The style apparently helps with
On 8/23/23 11:27 AM, Felix Lechner via Development of GNU Guix and the
GNU System distribution. wrote:
* Encourage upstream communities like "Guix 'R Us"
Every contributor should have their own channels for packages [1] and
for Guix. [2] Testing patches before they are submitted would vastly
August 24, 2023 3:57 PM, "Martin Baulig" wrote:
> Hello,
>
> About 2–3 months ago, I got an initial prototype of Bacula working on GNU
> Guix. I had the Bacula
> Director, two separate Storage Daemons and the Baculum web interface running
> in a GNU Guix VM on my
> Synology NAS.
I had to
> > Although now, just a few hours later, I'm having second thoughts on
> > this. When you really think about it, it's very unlinkely that some
> > user would prefer typing something like
> >
> > guix install
> >
Well, what I realized right now is that this sort of "transparency"
may not even have to be handled by guix at all. If we remember the
fact that we're on a unix-based system, a user who really wants to
install some piece of software with a unicode name, but doesn't know
how to type the requisite
Hi,
A couple of small early-morning (for me) comments below... not for or against
the idea of percent encoding, but as a little bit of food for thought while
pondering how to handle Unicode in package names and/or store paths.
On Friday, August 25th, 2023 at 2:01 PM, Eidvilas Markevičius
Hi Attila,
Attila Lendvai writes:
> i couldn't even find out which tools are used by those who are
> comfortable with the email based workflow. i looked around once, even
> in the manual, but maybe i should look again.
I can only speak for myself here, but I tend to use magit[0] from inside
Zhu Zihao writes:
> and AFIAK, Maxime Devos is working on new build system called
> "Antioxidant", which can build rust application without cargo (Yes,
> invoke rustc directly!), The new build system will cache the rlib
> intermediate result of crate and share between different builds.
Sadly, I
Although now, just a few hours later, I'm having second thoughts on
this. When you really think about it, it's very unlinkely that some
user would prefer typing something like
guix install
%D0%B8%D0%BC%D0%B0%D0%B3%D0%B8%D0%BD%D0%B0%D1%80%D0%B8-%D0%BF%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC
over
I once tried setting up kerberized nfsv4 and ended up falling down an
endless rabbit hole and eventually gave up. Instead, I encrypted nfs
using wireguard.
https://alexdelorenzo.dev/linux/2020/01/28/nfs-over-wireguard.html
Very impressive post though!
> For this, I either go to issues.guix.gnu.org to download the newest patches,
> in case the message is not in my inbox.
some patchsets evolve a lot, and there are countless messages where obsolete
patche versions are intermingled with non-obsolete discussion...
> Otherwise I do not get your
Jonas Møller writes:
> Hi Guix! Why does cargo-build-system need #:cargo-inputs specified in the
> package definition? This seems like a big
> mistake for a couple of reasons.
Just like the nice people in mail list explained, when building a
package, Guix builders are not allowed to connect
> I feel like the advantages of a email-based workflow nowadays is more on
> the maintainer side of things (as managing large projects is easier
another thing worth pointing out here is that the harder it is to test a
submitted patchset locally, the fewer non-committer reviews will happen.
and
Hello,
just a quick reply with what I do personally as one irrelevant data point :)
Am Fri, Aug 25, 2023 at 08:07:53AM + schrieb Attila Lendvai:
> i couldn't even find out which tools are used by those who are comfortable
> with the email based workflow. i looked around once, even in the
On Fri, Aug 25, 2023 at 11:37 AM Nathan Dehnel wrote:
>
> What you could do is implement percent encoding:
> https://en.wikipedia.org/wiki/Percent-encoding
> -Allows you to store package titles in any language in an encoded form
> -Allows the titles to be typed on latin keyboards
> -Allows the
> Now you might say that this leads to less diversity in the team of
> committers and maintainers as you need a certain level of privilege to
> seriously entertain the idea of dedicating that much time and effort to
> a project and I agree, but I also think this is a bigger reality of
> volunteer
What you could do is implement percent encoding:
https://en.wikipedia.org/wiki/Percent-encoding
-Allows you to store package titles in any language in an encoded form
-Allows the titles to be typed on latin keyboards
-Allows the packages to be accessed through URIs in the future without
causing
another +1 for the general sentiment of Katherine's message.
> I am all for it if it supplements the email based workflow (every
> time I need to do a modern style pull request type action, I am
> completely out of my depths and lost in the web interfaces...).
in my experience learning the
28 matches
Mail list logo
