From: ng0 <ng0@n0.is>
To: Gammel Holte <gammel.holte@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Packaging LyX
Date: Mon, 25 Dec 2017 13:41:37 +0000 [thread overview]
Message-ID: <20171225134137.mfzapdewwpbbdf33@abyayala> (raw)
In-Reply-To: <CAGFCsG86zHd9S__zxnTWKhQ8B16jPH-cMtZd+LeVDRRA=QruUw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1644 bytes --]
Gammel Holte transcribed 2.0K bytes:
> On Fri, Dec 22, 2017 at 7:42 PM, ng0 <ng0@n0.is> wrote:
>
> Thanks for your comments. I will address those before I circulate a patch.
>
> > Is this python-2 only? If not, could you explain why you picked 2 and not
> 3
> > (2 is on its way out in 20 months).
>
> LyX is sadly not ready for Python 3 yet. It will be soon, but there are
> still
> tickets open to support it: https://www.lyx.org/trac/ticket/9006
>
> Furthermore, I've tested LyX with Python 3 and it breaks.
Okay, no problem.
> Any hints on how to wrap the LyX package output so that it binds to the
> Python input, instead of looking for it at runtime, like the Nix package
> does?
>
> https://github.com/NixOS/nixpkgs/blob/86da6d441f7a248b02d545ac1b2c90ef27f42d0b/pkgs/applications/misc/lyx/default.nix
It depends. I have no time to look at the code (to see where python
is required, how much of it (modules etc)), but we have multiple
options, including:
1. Wrap the program. One of many examples:
https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/gnuzilla.scm#n759
2. patch calls of 'python' to the gnu-store python executable. I can see this
failing if python modules are required to be present and not just python.
3. Search for 'wrap' in the source checkout of Guix. You will find commits like
0498d24866c4955faee95a4fc19ff6817e5483d2
(https://git.savannah.gnu.org/cgit/guix.git/commit/gnu/packages?id=0498d24866c4955faee95a4fc19ff6817e5483d2)
--
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
WWW: https://n0.is
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-12-25 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 15:44 Packaging LyX Gammel Holte
2017-12-22 18:42 ` ng0
2017-12-22 22:49 ` Gammel Holte
2017-12-25 13:41 ` ng0 [this message]
2017-12-22 19:48 ` Danny Milosavljevic
2017-12-22 22:20 ` Gammel Holte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171225134137.mfzapdewwpbbdf33@abyayala \
--to=ng0@n0.is \
--cc=gammel.holte@gmail.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).