unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Guix Devel <guix-devel@gnu.org>
Subject: (propagated) 'inputs' depends on 'outputs'?
Date: Sat, 13 Jun 2020 13:01:01 +0200	[thread overview]
Message-ID: <CAJ3okZ38+VhW+Gq7PtPwx+AUAuV3pnzhwCGYCmd66u0uyA7ycA@mail.gmail.com> (raw)

Dear,

My question is: is it possible to specify 'inputs' only for specific 'outputs'?

Well, I think that the answer is no because build-time vs install-time
but I could have wrong and/or someone could have a fix for me. :-)


As an exemple, give a look at the package "git".  Because it has
several 'outputs' ("send-email", "svn", etc.), the list of "inputs"
provides e.g., "subversion" even if I am only interested by
"git:send-email".  This matters about closure (bandwidth, rebuild,
etc.).

I do not have an example at hand, but I think that if one package has
2 outputs '("out" "doc")' and the documentation requires heavy TeX
then I cannot work only on the "out" without downloading all the
documentation dependencies, i.e.,

   guix environment foo

could eat all my resources even if I am not interested by the
documentation part.


Another example is the package "emacs-helm-bibtex" which propagated
both Helm and Ivy completion backends.  Well, for example if the
'outputs' list is '("out" "helm" "ivy")' then the user could install
only the Ivy backend with:

   guix install emacs-helm-bibtex:ivy

without propagating the full 'emacs-helm' package.  Well, from my
understanding, the way is to create another package using 'inherit'
and remove the unnecessary part and then install with:

   guix install emacs-helm-bibtex-ivy

And same strategy the former Git example.


Well, it is already possible to test of some variables and set
different inputs,  See for example the package 'ncurse'.  Hopefully it
is possible because it is intensively used for cross-compiling. :-)


Thank you in advance for any tips. :-)

All the best,
simon


             reply	other threads:[~2020-06-13 11:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-13 11:01 zimoun [this message]
2020-06-13 11:16 ` (propagated) 'inputs' depends on 'outputs'? Christopher Baines
2020-06-16 12:31   ` zimoun
2020-06-16 15:34     ` Ricardo Wurmus
2020-06-16 15:52       ` zimoun
2020-06-13 11:38 ` Julien Lepiller
2020-06-16 12:41   ` zimoun
2020-06-16 14:28     ` Julien Lepiller
2020-06-16 15:45       ` zimoun
2020-06-19 20:47         ` Ludovic Courtès
2020-06-19 21:44           ` zimoun

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=CAJ3okZ38+VhW+Gq7PtPwx+AUAuV3pnzhwCGYCmd66u0uyA7ycA@mail.gmail.com \
    --to=zimon.toutoune@gmail.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).