Hi Martin,
> But if I run `xelatex mydoc.tex`, it complains about the missing .sty
file.
Try the TEXINPUTS environment variable. It is useful for specifying
extra paths.
The compilation command is:
$ TEXINPUTS=~/.guix-profile/share/texmf//: xelatex mydoc.tex
I use this method for documents
Hi Guix,
A lesson learnt from a previous update process [1] was; do not leave it
too long between 'guix pull' updates.
However, I have one system running Ubuntu 16.04 and Guix v0.12 that I
am trying to update. As root:
$guix package --list-installed
glibc-utf8-locales 2.25out /gn
Hi Konrad,
Thank you for your help.
> I have had similar problems as well in the past. The one recipe that
> has always worked (aside from one case of a machine with very limited
> disk space) is temporarily using a Guix compiled from source code.
I have hit a snag. At the compile stage I do:
Hi Ricardo,
Thank you for your help.
> I’m in the same situation upgrading a machine that didn’t have an
> Internet connection for months.
>
> Here’s what I do:
>
> - use a git checkout to jump to commit
> b0cb92b2d43a2c4d5fa9b3f8c04c5732c60061e7, which adds guile-gcrypt
>
> - ./bootstrap &&
Hi Guix,
Got it! I have been able to upgrade from version 0.12 to version 0.16.
I used 'guix copy' to copy a recent guix on a local server. Thank you
Gabor for the suggestion. The steps I followed were:
i) generate signing keys on both systems
ii) copy across public keys and authorize on each
Hi All,
I am in the middle of upgrading##SELECTION_END## the Gmsh package in
Guix. I have cloned the Guix repository, set up a profile for
development, and run bootstrap, configure and make. In setting up the
build environment for Gmsh, using 'guix environmnet ...', there are
surprising collisio
>
>
> So you can safely keep going. :-)
>
>
Thank you Ludo; I pressed on within the environment, ignoring the
collisions for now:
$ ./pre-inst-env guix build -K gmsh
The build succeeds. Then, to check:
$ GUILE_LOAD_PATH=$HOME/.guix-profile/share/guile/site/2.0 ./pre-inst-
env guix lint gmsh
N
Hi,
I am attempting to package the OpenCASCADE-OCE library for Guix using
the Nix opencascade_oce package as a starting point. I have a standard
Guix installation, a standard Nix installation plus the Guix source to
work on separately. opencascade_oce is not installed in the Nix store.
The Nix
Thank you, Ludo.
I have:
$ git describe
v0.11.0-3373-g2df3d14
My Nixpkgs directory is not managed by git. It was installed by the Nix
install script. It seems to have the same structure as the Github repository:
$ ls /home/paul/.nix-defexpr/channels/nixpkgs
doc maintainers pkgs README.md
I have tried updating my local directory with 'nix-channel
--update'.
No change; the full nix-instantiate command does not terminate.
The git commit of (in /home/paul/.nix-
defexpr/channels/nixpkgs/.version-suffix) is now 497e6d2.
Also, if I remove '--strict' from the nix-instantiate comm
Hi Ludo,
> >
> > I have noticed that the non-termination problem is not confined to
> > the
> > opencascage_oce package. If I try
> >
> > $ nix-instantiate --strict --eval --xml -A guile
> > /home/paul/.nix-defexpr/channels/nixpkgs
> >
> > that does not terminate either.
> Does it just take lon
11 matches
Mail list logo