unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Taylan Ulrich Kammer <taylanbayirli@gmail.com>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Add guile-emacs!
Date: Thu, 14 May 2015 22:06:33 +0200	[thread overview]
Message-ID: <87siayhqk6.fsf@gmail.com> (raw)
In-Reply-To: <87vbfvdugp.fsf@earlgrey.lan> (Christopher Allan Webber's message of "Thu, 14 May 2015 10:53:43 -0500")

Christopher Allan Webber <cwebber@dustycloud.org> writes:

>>> +(define-public guile-for-guile-emacs
>>> [...]
>>> +    (inputs
>>> +     `(("gettext" ,gnu-gettext)
>>
>> Sure it shouldn't be in native-inputs?  I'm guessing autogen uses it.
>
> So, could someone describe the difference between inputs and
> native-inputs?  The manual provides no clarity!  I never know where it
> goes and why... I just mime what other packages are doing.

Perhaps a bug report should be opened about the absence of documentation
on native and propagated inputs...

When an input is in native-inputs instead of inputs, then it is ensured
during cross-compilation that the version present during the build of
the package will be for the platform on which the build is happening;
this is necessary if executables from the input will be run during the
build, such as the autotools suite, bash, gcc, etc.  (The latter are
implicit native inputs of the gnu-build-system AFAIK.)

Gettext will probably be run on the source code to extract localizable
strings; if so then it should be a native input.

If it were just a shared library like libpng, or a program that will be
used during use of the package (such as the 'git' input to 'magit'),
then it needn't be a native input since no executables from it will be
run during the build and it doesn't matter if it's for another platform.

Hope that helps!
Taylan

  reply	other threads:[~2015-05-14 20:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-10 19:35 [PATCH] Attempt at packaging guile-emacs (needs help) Christopher Allan Webber
2015-05-10 21:51 ` Mark H Weaver
2015-05-11  2:29   ` Christopher Allan Webber
2015-05-14  0:01 ` [PATCH] Add guile-emacs! Christopher Allan Webber
2015-05-14  8:56   ` Taylan Ulrich Kammer
2015-05-14 15:53     ` Christopher Allan Webber
2015-05-14 20:06       ` Taylan Ulrich Kammer [this message]
2015-05-14 20:52         ` Taylan Ulrich Kammer
2015-05-15 10:13       ` Ludovic Courtès
2015-05-19 17:29     ` Christopher Allan Webber
2015-05-19 18:29       ` Taylan Ulrich Bayırlı/Kammer
2015-05-19 19:41         ` Christopher Allan Webber
2015-05-19 20:24           ` Taylan Ulrich Bayırlı/Kammer
2015-05-20 12:22             ` Ludovic Courtès
2015-05-23  7:26   ` Feng Shu
2015-05-23 17:21     ` Christopher Allan Webber

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=87siayhqk6.fsf@gmail.com \
    --to=taylanbayirli@gmail.com \
    --cc=cwebber@dustycloud.org \
    --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).