From: Ricardo Wurmus <rekado@elephly.net>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org, Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Re: Python applications that are also libraries
Date: Fri, 06 Apr 2018 14:12:06 +0200 [thread overview]
Message-ID: <871sfsjzzd.fsf@elephly.net> (raw)
In-Reply-To: <878ta0aec8.fsf@gmail.com>
Chris Marusich <cmmarusich@gmail.com> writes:
> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
>
>> we have a bunch of packages that are used both as applications and as
>> Python libraries. An example is “deeptools”.
>
> I took a brief peek at deeptools. It looks like there are programs in
> bin, and libraries in lib. Why can't we just split them into two
> outputs? For example, put the libraries into the default "out" output
> and the programs into the "bin" output.
The programs in “bin” use the libraries in “lib”. The binaries aren’t
big, so separating them from the lib output provides hardly any benefit.
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.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2018-04-06 13:58 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 [this message]
2018-04-07 9:27 ` Hartmut Goebel
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=871sfsjzzd.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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).