unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: guix-devel@gnu.org
Subject: Re: Python applications that are also libraries
Date: Sat, 7 Apr 2018 11:27:37 +0200	[thread overview]
Message-ID: <6845537d-5c7b-53e3-9f31-07fa0ba889af@crazy-compilers.com> (raw)
In-Reply-To: <871sfsjzzd.fsf@elephly.net>

Am 06.04.2018 um 14:12 schrieb Ricardo Wurmus:
> The point here is that in the library case inputs must be propagated,
> whereas in the case where only the executables are used the inputs don’t
> have to be propagated.
>
> Separating them in two outputs doesn’t address this problem as far as I
> can see.
Using the venv-based wrapper I describe in
<https://lists.gnu.org/archive/html/guix-devel/2018-02/msg00456.html
could avoid propagating for the scripts - but not for the libs.

IMHO it does not make much sense having "script" packages without
propagation, as we still need "libs" packages with propagation. Even if
"deeptools:script" would not propagate its inputs, "somepackage:lib"
(required by "deeptools:script") would still need to propagate its
inputs. Thus nothing gained.

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

      reply	other threads:[~2018-04-07  9:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-04  9:36 Python applications that are also libraries Ricardo Wurmus
2018-04-04 11:36 ` Hartmut Goebel
2018-04-04 20:13   ` Ricardo Wurmus
2018-04-05  7:05     ` Hartmut Goebel
2018-04-06  9:12 ` Chris Marusich
2018-04-06 10:11   ` Hartmut Goebel
2018-04-06 12:12   ` Ricardo Wurmus
2018-04-07  9:27     ` Hartmut Goebel [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=6845537d-5c7b-53e3-9f31-07fa0ba889af@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.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).