gfp writes:
Hi,
1.
Approx. 2 years ago some Guixers proposed to create profiles in
order
to have not too many packages in the main profile, which makes
it
easier to update the profile. If during updating the profile one
package creates trouble, the whole updating process stops. I had
those
Hi Marek,
Marek Paśnikowski writes:
I copied and extended the invocation of "make" from the
gnu-build-system:
(arguments
(list
#:phases '(modify-phases
%standard-phases
(add-before
'build
'make-project
(lam
Hi,
1.
Approx. 2 years ago some Guixers proposed to create profiles in order to
have not too many packages in the main profile, which makes it easier to
update the profile. If during updating the profile one package creates
trouble, the whole updating process stops. I had those trouble several
Hi,
thanks for explaining more.
`export
XDG_DATA_DIRS=$HOME/gfp/Projekte/Calibre:$HOME/gfp/Projekte/Emacs:$XDG_DATA_DIRS`
I would have to write: `export
XDG_DATA_DIRS=$HOME/gfp/Projekte/Calibre/guix-profile/share:$HOME/gfp/Projekte/Emacs/guix-profile/share:$XDG_DATA_DIRS`
because In every
On poniedziałek, 9 grudnia 2024 17:52:36 CET you wrote:
> Hi Marek,
>
> On Mon, Dec 9, 2024, at 4:47 PM, Marek Paśnikowski wrote:
> > Does this mean I will have to `make` the project before `building go`?
>
> I'm not sure how the go-build-system interacts with stuff like this, or what
> complexit
Hi gfp,
gfp writes:
I have got 17 Profiles in:
/home/gfp/Projekte/Calibre
/Emacs
/Libreoffice
etc.
Would that mean to sorce all 17 profiles in one go? or only two
at a time?
I agree with Steve: you shouldn’t use profiles like this. B
Hi Marek,
On Mon, Dec 9, 2024, at 4:47 PM, Marek Paśnikowski wrote:
>
> Does this mean I will have to `make` the project before `building go`?
>
I'm not sure how the go-build-system interacts with stuff like this, or what
complexity the Makefile may bring. Probably the simplest thing is to add
On poniedziałek, 9 grudnia 2024 17:38:20 CET Ian Eure wrote:
> Hi Marek,
>
> On Mon, Dec 9, 2024, at 4:24 PM, Marek Paśnikowski wrote:
> > I managed to break through version incompatibilites thanks to discovery of
> > the guix:build-system:go:go-version->git-ref function, which allowed me
> > to u
Hi Marek,
On Mon, Dec 9, 2024, at 4:24 PM, Marek Paśnikowski wrote:
> I managed to break through version incompatibilites thanks to discovery of
> the
> guix:build-system:go:go-version->git-ref function, which allowed me to use
> the
> specifications in go.mod files directly.
>
> I am currentl
I managed to break through version incompatibilites thanks to discovery of the
guix:build-system:go:go-version->git-ref function, which allowed me to use the
specifications in go.mod files directly.
I am currently blocked on what seems to be an actual upstream coding bug, for
which I filed a re
Dear Edouard,
Thanks a lot. That helped.
But - in my opinion - it also shows that there is something
missing, if you can start a service via the system configuration
but cannot get information about it other than by hand.
Cheers
Alex
On Mon, Dec 09 2024, 11:50:45, Edouard Klein wrote:
Hi
Hi Julien, thank you! That does work.
So if I understand correctly, #$ doesn't only escape #~ but also unquotes
quoted lists. That's good to know! It's possible a good fraction of my
recurring troubles with gexps came from not realizing that.
On Mon, Dec 09 2024, Julien Lepiller wrote:
> Hi Yu
Hi Yulran,
I think this is related to how gexps are expanded. In your first gexp, you use
#$accounts, which expands to ("account1" "account2"), and it's interpreted as a
procedure call.
Untested, but '#$accounts should work.
It might be easier to work with a single gexp, like so:
#~(job '(nex
Hi guix,
I'm having trouble with nesting g-expressions when defining a mcron job. I want
the job to run the same "mastodon-archive" commands for several accounts, so I
define a list of accounts and use 'map' to build the complete command. This
works well when there are only strings involved, bu
Hello Tim,
Am Sun, Dec 08, 2024 at 07:29:47PM -0500 schrieb Timothy Washington:
> (define vm-image
> (image
>(operating-system physical-operating-system)
>(format qcow2-image-type)
>(size (* 10 (expt 2 30)
looking at the code, I see this in gnu/image.scm:
(define-record-type*
Hi Timothy,
Last time I generated a system image, I ran this command :
guix system image --image-size=10G --image-type=qcow2 basic.scm
Does it help ?
Jérémy
Hi,
It turned out I sourced my completion incorrectly. When I changed my setup as
per Nilss suggestion the issue stopped. I assume by sourcing it this way this
issue is already taken into account and resolved elsewhere.
lördag den 07 december 2024 skrev Hilton Chain:
> * gnu/packages/image.scm
fredag den 06 december 2024 skrev Tobias Geerinckx-Rice:
> libsixel, through mpv, but you misunderstand me, there's nothing
> wrong with it. It's the canary in the coal mine.
>
> The 'broken code' I meant is this
>
>>for f in "$HOME"/.guix-profile/etc/bash_completion.d/* ; do
>>. "$f"
>>do
18 matches
Mail list logo
