2017-12-22 15:44:47 UTC
I'm planning to switch a dozen or so machines to GuixSD.
The only major package my users are missing is LyX (a LaTeX editor, see
https://www.lyx.org/) so I packaged it, and it works fine. See code below.
I would appreciate some help wrapping python. I'm familiar how to do this
in Nix, but not in Guix. Despite requiring a python interpreter for during
build, LyX dynamically looks for a python interpreter at runtime.
Obviously, it'd be desirable to link LyX to the python instance used as
input. For the record this is the LyX package in Nixpkgs:
I also had some doubts when packaging:
- Is a xz source preferred to a gz one?
- Nix uses qtcore and qtsvg as inputs, but if I use these in Guix (in place
of the whole qt) then LyX can't render its icons (svgz)
There are another minor TODOs:
- Transition to proper package and define-public syntax, as I was
installing with guix package -f
- Decide whether the package should live in tex.scm or elsewhere
Once this is done, I'm happy to submit a proper patch.
(guix build-system gnu)
(gnu packages algebra)
(gnu packages compression)
(gnu packages pkg-config)
(gnu packages python)
(gnu packages qt))
(uri (string-append "ftp://ftp.lyx.org/pub/lyx/stable/2.2.x/lyx-"
(inputs `(("pkg-config" ,pkg-config)
(arguments `(#:configure-flags (list "--enable-qt5")))
(synopsis "An advanced WYSIWYM document processor and LaTeX front-end")
(description "LyX is a document processor that encourages an approach
to writing based on the structure of your documents (WYSIWYM) and not
simply their appearance (WYSIWYG). LyX combines the power and
flexibility of TeX/LaTeX with the ease of use of a graphical