unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jakub Kądziołka" <kuba@kadziolka.net>
To: Leo Famulari <leo@famulari.name>
Cc: 39378@debbugs.gnu.org
Subject: [bug#39378] [PATCH] gnu: Add FIM.
Date: Fri, 10 Jul 2020 23:38:02 +0200	[thread overview]
Message-ID: <20200710213802.djp7swkyypxqesyv@gravity> (raw)
In-Reply-To: <0be1c20da4fab4533541600882fc383ab2f59a84.1580511103.git.leo@famulari.name>

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

On Fri, Jan 31, 2020 at 05:51:51PM -0500, Leo Famulari wrote:
> * gnu/packages/image-viewers.scm (fim): New variable.
> ---
>  gnu/packages/image-viewers.scm | 41 ++++++++++++++++++++++++++++++++++
>  1 file changed, 41 insertions(+)

Thanks!

> +    (inputs
> +     `(("aalib" ,aalib)
> +       ("alsa-lib" ,alsa-lib)
> +       ("giflib" ,giflib)
> +       ("libexif" ,libexif)
> +       ("libjpeg" ,libjpeg-8)

libjpeg-8 doesn't exist anymore. The package builds fine when this is
replaced by libjpeg-turbo, and it seems to work, too, in my limited
testing. Is such a change reasonable in your opinion?

From the build log:

|         use 'inkscape' for SVG files        : no
|         use 'fig2dev' for FIG files         : no
|         JP2 (JPEG-2K) file support (JasPer) : no

Is there a specific reason we don't want support for these formats?

Regards,
Jakub Kądziołka

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2020-07-10 21:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-31 22:51 [bug#39378] [PATCH] gnu: Add FIM Leo Famulari
2020-01-31 23:27 ` Jonathan Brielmaier
2020-02-02  6:05   ` Leo Famulari
2020-07-10 21:38 ` Jakub Kądziołka [this message]
2021-12-29 19:40 ` bug#39378: " Leo Famulari

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=20200710213802.djp7swkyypxqesyv@gravity \
    --to=kuba@kadziolka.net \
    --cc=39378@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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).