Nils Gillmann writes:
>> If you have a file “core/lang-perl/perl.scm” and the module is called
>> “(core lang-perl perl)” then you should not have “core” itself on
>> GUIX_PACKAGE_PATH but its parent directory.
>
> In my example (pkgs lang-perl perl) itself had the parent directory "pkgs".
> I a
Ricardo Wurmus transcribed 1.0K bytes:
>
> Nils Gillmann writes:
>
> > Here's what's happening now:
> >
> > I took my perl module which is in "pkgs/lang-perl/perl.scm", which contains
> > our basic perl packages,
> > and moved ( + renamed ) them into (core lang-perl perl) in a new directory.
>
Nils Gillmann writes:
> Here's what's happening now:
>
> I took my perl module which is in "pkgs/lang-perl/perl.scm", which contains
> our basic perl packages,
> and moved ( + renamed ) them into (core lang-perl perl) in a new directory.
>
> If I run GUIX_PACKAGE_PATH="/home/user/src/core" pack
Chris Marusich transcribed 3.0K bytes:
> Nils Gillmann writes:
>
> > Hi,
> >
> > I'm not sure if guile-users / -dev liste is more appropriate. If it is, let
> > me know.
> >
> > I'm currently still using GUIX_PACKAGE_PATH until I got my layout all set
> > up.
> > There's an issue that I can't s
Nils Gillmann transcribed 1.9K bytes:
> Nils Gillmann transcribed 1.4K bytes:
> > Nils Gillmann transcribed 2.1K bytes:
> > > Okay, here's what I learned:
> > >
> > > * except for source code, the modules itself in Guile aren't very
> > > * detailed documented. The documentation is good, but... .
Nils Gillmann transcribed 1.4K bytes:
> Nils Gillmann transcribed 2.1K bytes:
> > Okay, here's what I learned:
> >
> > * except for source code, the modules itself in Guile aren't very
> > * detailed documented. The documentation is good, but... ... it's
> > * nowhere mentioned that you can have
Nils Gillmann transcribed 2.1K bytes:
> Okay, here's what I learned:
>
> * except for source code, the modules itself in Guile aren't very
> * detailed documented. The documentation is good, but... ... it's
> * nowhere mentioned that you can have a module (foo bar baz) and
> * possibly also (foo
Okay, here's what I learned:
* except for source code, the modules itself in Guile aren't very
* detailed documented. The documentation is good, but... ... it's
* nowhere mentioned that you can have a module (foo bar baz) and
* possibly also (foo bar baz kim) but (foo baz bar bar) will lead to
*
Chris Marusich transcribed 2.3K bytes:
> Nils Gillmann writes:
>
> > Anyways, in which section of the guile Manual would I find "pk"? I've
> > done surprisingly little debugging with Guile itself so far.
>
> Unfortunately, pk isn't (yet?) documented. It apparently stands for
> "peek stuff". It
Nils Gillmann writes:
> Anyways, in which section of the guile Manual would I find "pk"? I've
> done surprisingly little debugging with Guile itself so far.
Unfortunately, pk isn't (yet?) documented. It apparently stands for
"peek stuff". It prints and returns the value passed to it. It's a
u
Chris Marusich transcribed 3.0K bytes:
> Nils Gillmann writes:
>
> > Hi,
> >
> > I'm not sure if guile-users / -dev liste is more appropriate. If it is, let
> > me know.
> >
> > I'm currently still using GUIX_PACKAGE_PATH until I got my layout all set
> > up.
> > There's an issue that I can't s
Nils Gillmann writes:
> Hi,
>
> I'm not sure if guile-users / -dev liste is more appropriate. If it is, let
> me know.
>
> I'm currently still using GUIX_PACKAGE_PATH until I got my layout all set up.
> There's an issue that I can't seem to get rid of, I'll try my best to
> describe it now:
>
>
Hi,
I'm not sure if guile-users / -dev liste is more appropriate. If it is, let me
know.
I'm currently still using GUIX_PACKAGE_PATH until I got my layout all set up.
There's an issue that I can't seem to get rid of, I'll try my best to describe
it now:
I have package definitions in 2 reposito
13 matches
Mail list logo
