contain a bunch
> of package definitions.
>
> This would replace the need to set GUIX_PACKAGE_PATH (or pass -L) to a
> directory containing a module, and set up package transformations for
> each package.
>
> It would also be lighter than requiring the use of a manifest, which
Hello,
Sarthak Shah writes:
> Hello,
>
>> By separate file or stdin your really mean stdin, correct? As in:
>>
>> --8<---cut here---start->8---
>> guix something < args.txt or
>> echo "$args" | guix something
>> --8<---cut here---end--
Hi Ricardo,
Ricardo Wurmus writes:
> Maxim Cournoyer writes:
>
>>> Considering that the transformations API assumes that you understand
>>> that higher order functions exist and what to do with them, I think it
>>> would be good to offer a slightly less advanced method of overriding
>>> package
Hello,
> By separate file or stdin your really mean stdin, correct? As in:
>
> --8<---cut here---start->8---
> guix something < args.txt or
> echo "$args" | guix something
> --8<---cut here---end--->8---
>
> One note: since t
Hello!
Thanks for the CC, Josselin!
I like Maxim's idea of providing all kinds of arguments through a separate
file or stdin.
Here's a tiny proof-of-concept script implementing that:
-guix-shell-with-args.sh
#!/usr/bin/env bash
argstr=""
while read line
do
argstr="$argstr $line"
done < "$
Hi!
Sarthak Shah writes:
> Hello!
> Thanks for the CC, Josselin!
> I like Maxim's idea of providing all kinds of arguments through a separate
> file or stdin.
> Here's a tiny proof-of-concept script implementing that:
> -guix-shell-with-args.sh
> #!/usr/bin/env bash
> argstr=""
> while r
Maxim Cournoyer writes:
>> Considering that the transformations API assumes that you understand
>> that higher order functions exist and what to do with them, I think it
>> would be good to offer a slightly less advanced method of overriding
>> packages.
>>
>> Manifests can do anything, but thi
Hi!
Ricardo Wurmus writes:
> Maxim Cournoyer writes:
>
>> Hi Ricardo,
>>
>> Ricardo Wurmus writes:
>>
>>> Hi Guix,
>>>
>>> when using package transformations the command line can become crowded
>>> very quickly. Sometimes
Maxim Cournoyer writes:
> Hi Ricardo,
>
> Ricardo Wurmus writes:
>
>> Hi Guix,
>>
>> when using package transformations the command line can become crowded
>> very quickly. Sometimes I would like to be able to provide a file
>> containing a
Hi Ricardo,
Ricardo Wurmus writes:
> Hi Guix,
>
> when using package transformations the command line can become crowded
> very quickly. Sometimes I would like to be able to provide a file
> containing a set of alternative packages that are used recursively in
> the packag
Hi,
Ricardo Wurmus skribis:
> when using package transformations the command line can become crowded
> very quickly. Sometimes I would like to be able to provide a file
> containing a set of alternative packages that are used recursively in
> the package dependency graph, as
Hi Ricardo,
Ricardo Wurmus writes:
> Hi Guix,
>
> when using package transformations the command line can become crowded
> very quickly. Sometimes I would like to be able to provide a file
> containing a set of alternative packages that are used recursively in
> the packag
Hi Guix,
when using package transformations the command line can become crowded
very quickly. Sometimes I would like to be able to provide a file
containing a set of alternative packages that are used recursively in
the package dependency graph, as some sort of override.
What do you think about
Hi,
zimoun skribis:
> There is several ways to have package transformations at the manifest
> level. One is:
>
> (use-modules (guix transformations))
>
> (define transform1
> (options->transformation
> '((with-c-toolchain . "hello=gcc-toolchain@8&q
On Tue, Mar 16 2021, Ludovic Courtès wrote:
> You may also like the new ‘--with-latest’ package transformation
> option. :-)
I really like package transformations but is there a way to use specify
them with Guile so I can use them with `guix home`[1] or in manifests?
Ccing guix-dev
On Tue, Mar 16 2021, zimoun wrote:
>> I really like package transformations but is there a way to use specify
>> them with Guile so I can use them with `guix home`[1] or in manifests?
>
> There is several ways to have package transformations at the manifest
> le
Hi,
On Tue, 16 Mar 2021 at 17:46, Xinglu Chen wrote:
> On Tue, Mar 16 2021, Ludovic Courtès wrote:
>
> > You may also like the new ‘--with-latest’ package transformation
> > option. :-)
>
> I really like package transformations but is there a way to use specify
> t
Ricardo Wurmus skribis:
> Ludovic Courtès writes:
>
>> I’ve pushed my “train hacks”, which are a continuation of refactoring
>> work I had done in December (ca. 64ec0e2):
>>
>> • ‘guix build’ has a new ‘--with-input’ option to rewrite the
>> dependency graph so you can run:
>>
>> gui
Ludovic Courtès writes:
> I’ve pushed my “train hacks”, which are a continuation of refactoring
> work I had done in December (ca. 64ec0e2):
>
> • ‘guix build’ has a new ‘--with-input’ option to rewrite the
> dependency graph so you can run:
>
> guix build guix --with-input=guile=gui
Ludovic Courtès writes:
> Hello!
>
> I’ve pushed my “train hacks”, which are a continuation of refactoring
> work I had done in December (ca. 64ec0e2):
>
> • ‘guix build’ has a new ‘--with-input’ option to rewrite the
> dependency graph so you can run:
>
> guix build guix --with-input=
Efraim Flashner skribis:
> I looked over the commit but not deeply enough yet, would it be possible to
> use some of the logic in this to fix the package-with-python2 issue?
Nope!
> what about extending guix package so you could do `guix package -i $(guix
> build foo --with-input=bar=baz) --nam
On Mon, Feb 01, 2016 at 08:49:10AM -0500, Thompson, David wrote:
> Here's a potential solution for 'package-with-python2': module
> introspection. AIUI, the issue is that some Python 2 packages need
> extra manual tweaking, but 'package-with-python2' creates package
> variants without these tweaks
On Mon, Feb 1, 2016 at 11:35 AM, Efraim Flashner wrote:
> Not all of our python packages are in python.scm. Currently in
> guix/build-system/python.scm we have:
>
> (define package-with-python2
> ;; Note: delay call to 'default-python2' until after the 'arguments' field
> ;; of packages is ac
On Mon, 1 Feb 2016 08:49:10 -0500
"Thompson, David" wrote:
> On Mon, Feb 1, 2016 at 8:06 AM, Efraim Flashner wrote:
>
> > I looked over the commit but not deeply enough yet, would it be possible to
> > use some of the logic in this to fix the package-with-python2 issue?
>
> Here's a potentia
On Mon, Feb 01, 2016 at 08:49:10AM -0500, Thompson, David wrote:
> Also, somewhat unrelated, package-with-python2 could add setuptools as
> an input to these packages so we can remove all the unnecessary usage
> of it in Python 3 packages.
+1 as it is often needed and harmless when it is not neede
On Mon, Feb 1, 2016 at 8:06 AM, Efraim Flashner wrote:
> I looked over the commit but not deeply enough yet, would it be possible to
> use some of the logic in this to fix the package-with-python2 issue?
Here's a potential solution for 'package-with-python2': module
introspection. AIUI, the iss
On Mon, 01 Feb 2016 10:18:01 +0100
l...@gnu.org (Ludovic Courtès) wrote:
> Hello!
>
> I’ve pushed my “train hacks”, which are a continuation of refactoring
> work I had done in December (ca. 64ec0e2):
>
> • ‘guix build’ has a new ‘--with-input’ option to rewrite the
> dependency graph so y
Hello!
I’ve pushed my “train hacks”, which are a continuation of refactoring
work I had done in December (ca. 64ec0e2):
• ‘guix build’ has a new ‘--with-input’ option to rewrite the
dependency graph so you can run:
guix build guix --with-input=guile=guile-next
and guess what it
28 matches
Mail list logo