From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: inputs vs. native-inputs vs. propagated-inputs
Date: Fri, 17 Jun 2016 22:49:59 +0200 [thread overview]
Message-ID: <57646277.4020400@crazy-compilers.com> (raw)
In-Reply-To: <20160612195328.GB1615@jasmine>
Hallo Leo,
thanks for you answer.
Am 12.06.2016 um 21:53 schrieb Leo Famulari:
> 'Inputs' do typically get used at run-time, as do propagated-inputs.
>
> I found it hard to understand the distinctions by reading. It was only
> when I had been making packages for a while that I understood.
>
> I've tried to improve this text but I haven't come up with anything yet.
I'd try a text, but I did not really understand the difference yet.
>>> If so, how can I as a packager find out if eg. libBBB is only used at
>>> build time and libCCC need to be a propagated input?
> You will need at least a little knowledge about the programs you are
> packaging and how they are supposed to build and run. I read a bit about
> each program to guess about how libAAA uses it.
IC. I was hoping. I could just package some stuff without any knowledge.
E.g to make basic libraries and programs available so others can add
more programs. Obviously I was wrong here :-(
>
>> I'm the packager, so I'm the one who needs to *define* the dependencies.
>> There is no ‘guix gc –-references …’ I can query. So *I* need a way to
>> determine whether an input needs to be propagated or not.
> Test the program in an isolated environment and see if it works without
> propagating the inputs.
Thanks, this is a helpful tip.
> Also, once you've built the package, using `guix gc --references` is a
> good way to inspect it.
This is what I do not get: If I do not specify some dependency, how will
it be listed with `gc --references` (except the case there is another
dependency). And if `gc --references` would be able to find dependencies
I missed, why at all should one list dependencies?
> The type of input chosen by the packager does not dictate how libAAA
> uses the dependency. The package could erroneously retain a reference to
> a native-input like Automake, and `guix gc --references` will show you
> this.
>
> So, if libCCC appears in `guix gc --references /gnu/store/...-libAAA`,
> it's reasonable to guess that libCCC does not need to be propagated.
>
> Or, the package could lack a reference to something you *know* is needed
> at run-time. So you can address that with propagated-inputs or setting
> some build-time configuration.
>
> Is it making more sense?
It opens a window in the dust of incomprehension :-) But I need to thing
(and test) on this whole topic a lot more.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2016-06-17 20:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 9:07 inputs vs. native-inputs vs. propagated-inputs Hartmut Goebel
2016-06-12 12:38 ` 宋文武
2016-06-12 15:50 ` Hartmut Goebel
2016-06-12 19:53 ` Leo Famulari
2016-06-17 20:49 ` Hartmut Goebel [this message]
2016-06-17 23:34 ` Leo Famulari
2016-06-18 19:24 ` Ludovic Courtès
2016-06-19 3:57 ` Lukas Gradl
2016-06-19 13:44 ` Ludovic Courtès
2016-06-21 13:37 ` Lukas Gradl
2016-07-10 21:23 ` Chris Marusich
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=57646277.4020400@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=help-guix@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.
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).