unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Pierre-Henry F." <contact@phfrohring.com>
To: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: [HELP] Packaging mupdf
Date: Sat, 02 Mar 2019 20:15:06 +0000	[thread overview]
Message-ID: <z0_jUIF4KaBeXdxLrRzSF1cc_wwZGFOb8UOnPGpcyRbpoN5MFQy0-GwEyNtZ7OSWWD_dvDUDZXDpjbHzDG5itjpFvvoIyCH8WwMJjY_5tEU=@phfrohring.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]

Hello,

I'm trying to learn how to package code using Guix and packaging
mupdf doing do. I need some help to continue.

I've followed packaging tutorial for guix[1] and hopefully know
enough scheme (Racket in fact) to carry one.

The problem with the way mupdf is package today[2] is that it
does not include the patched version of freeglut that is
necessary for the copy-pasting functionality[3].

What does work is to follow the build instructions of mupdf[4]
which boils down to:

  git clone --recursive git://git.ghostscript.com/mupdf.git
  cd mupdf
  git submodule update --init
  sudo apt-get install mesa-common-dev libgl1-mesa-dev libglu1-mesa-dev xorg-dev libxcursor-dev libxrandr-dev libxinerama-dev
  make prefix=~/bin/mupdf install

So, I guess that the objective is to somehow make guix execute
the above script.

I've been wondering around in the doc of guix w/o much success.
Is there anyone that could help me out? I can document the thing
and post it on my blog or give it back here for anyone to do
anything with it, should it be of some use.

Many thanks,
PH

[1]: https://www.gnu.org/software/guix/blog/2018/a-packaging-tutorial-for-guix/
[2]: $ guix edit mupdf
[3]: https://bugs.archlinux.org/task/57227
[4]: https://mupdf.com/docs/building.html

[-- Attachment #2: Type: text/html, Size: 2040 bytes --]

             reply	other threads:[~2019-03-02 20:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-02 20:15 Pierre-Henry F. [this message]
2019-03-02 22:15 ` [HELP] Packaging mupdf Ricardo Wurmus
2019-03-03  8:52   ` Pierre-Henry F.
2019-03-03 14:30     ` Ricardo Wurmus
2019-03-04 17:09       ` Pierre-Henry F.

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='z0_jUIF4KaBeXdxLrRzSF1cc_wwZGFOb8UOnPGpcyRbpoN5MFQy0-GwEyNtZ7OSWWD_dvDUDZXDpjbHzDG5itjpFvvoIyCH8WwMJjY_5tEU=@phfrohring.com' \
    --to=contact@phfrohring.com \
    --cc=help-guix@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.
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).