unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: Guix-devel <guix-devel@gnu.org>, help-guix <help-guix@gnu.org>
Subject: Re: [video repo] when making videos inside container images break
Date: Wed, 6 Mar 2019 08:19:20 +0100	[thread overview]
Message-ID: <CAE4v=picfcSRzBkooyOs0UDBeya+4HuqQCGKYZ+LUVKfsoMoPA@mail.gmail.com> (raw)
In-Reply-To: <20190306074353.5e8aa545@alma-ubu>

Hello Björn,

Björn Höfling <bjoern.hoefling@bjoernhoefling.de> ezt írta (időpont:
2019. márc. 6., Sze, 7:44):
>
> On Sun, 3 Mar 2019 20:30:51 +0100
> Gábor Boskovits <boskovits@gmail.com> wrote:
>
>
> > Then I looked around the package definition of inkscape, where I found
> > no sign of cairo...
> >
> > I tried adding it to the container, and it seems to be working fine
> > here.
>
> Hi Gábor,
>
> thank you for that analysis! Do you think it would make sense to add
> cairo as as inputs or propagated-inputs for inkscape?

I don't know. Most of the functionality seems to be intact when it is missing.
However it would be nice to at least notify the user about the missing cairo,
and that it might break image funtionality. I am not in general very statisfied
when a program just picks up its runtime dependencies from whatever
environment it is run... but I feel it's not going to change soon.

Is there any way how we could extend a guix package receipe to list at least
the well-known optional runtime dependencies, and to describe what funtionality
do they add to a program, so the user could select what to install alongside?

>
> Björn

Best regards,
g_bor

      reply	other threads:[~2019-03-06  7:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-03  2:59 [video repo] when making videos inside container images break Laura Lazzati
2019-03-03 15:06 ` Gábor Boskovits
2019-03-03 16:19   ` Laura Lazzati
2019-03-03 17:12     ` Laura Lazzati
2019-03-03 18:44       ` Gábor Boskovits
2019-03-03 19:09         ` Laura Lazzati
2019-03-03 19:30           ` Gábor Boskovits
2019-03-03 23:39             ` Laura Lazzati
2019-03-06  6:43             ` Björn Höfling
2019-03-06  7:19               ` Gábor Boskovits [this message]

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='CAE4v=picfcSRzBkooyOs0UDBeya+4HuqQCGKYZ+LUVKfsoMoPA@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=bjoern.hoefling@bjoernhoefling.de \
    --cc=guix-devel@gnu.org \
    --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).