Hi,
On Tue, 07 Mar 2023 at 16:57, Przemysław Kamiński wrote:
> Starting download of /tmp/guix-file.TykbjO
> From
> https://hackage.haskell.org/package/servant-examples/servant-examples-0.1.0.0.tar.gz...
> download failed
> "https://hackage.haskell.org/package/servant-examples/servant-examples
As for an example. Clone this repository
https://github.com/sras/servant-examples
Then cd into it and run
cat servant-examples.cabal | guix import hackage -s -r
The '-s' option reads from stdin, the '-r' option imports everything
recursively.
It throws this output:
Starting download of /tm
Hi,
Przemysław Kamiński skribis:
> 3. I run `guix build -L -m manifest.scm
> (manifest only contains a reference to ghc-stuff.scm)
> 4. I get an error which looks like this:
> View build log at
> '/var/log/guix/drvs/j2/wa3vw49l78m85z74x91sklqxwhx87y-ghc-hwodr-0.1.0.drv.bz2'
>
> so I fire up
>
>
Hi,
On Fri, 03 Mar 2023 at 10:44, Przemysław Kamiński wrote:
> This is tedious. Is there a way to automate this a bit more?
Nothing I am aware of. Because Guix relies on some LTS, there is no
easy way, to my knowledge, to achieve what you would like. Somehow you
have to package by yourself an
> This is tedious. Is there a way to automate this a bit more?
Only slightly. Do remember, that Guix is purely functional. Your pain is with
the chain of dependencies.
I recently went through a similar ordeal while packaging an update to Nix. I
suggest to:
1. look up the dependency list on t
Hello,
I'm a Guix noob so please be patient :)
I currently want to use Guix to do some reproducible package management
for my code.
So far my workflow is this:
1. I want to build some Haskell code
2. I need custom libs, so I write a simple package file (ghc-stuff.scm)
like this one:
(defin
