From: Nikita Karetnikov <nikita@karetnikov.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guix@gnu.org
Subject: Re: GNU Bazaar doesn't support the GNU build system
Date: Wed, 23 Jan 2013 01:13:07 -0500 [thread overview]
Message-ID: <874ni8toj4.fsf@karetnikov.org> (raw)
In-Reply-To: <871udgvsla.fsf@gnu.org> ("Ludovic Courtès"'s message of "(unknown date)")
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
> I realize this is a bit more involved than “just” packaging the thing,
> but it will be useful in the long run.
I'm missing the big picture. That's the main problem. What will happen
when I run 'guix-package -i hello'?
AFAICT, '(build-system gnu-build-system)' calls 'gnu-build' with the
corresponding arguments. But I can't find where this actually happens.
I assume that 'gnu-build' will call '%standard-phases' (from
'gnu-build-system.scm') if I don't specify any arguments. Then
'%standard-phases' will call the functions like 'set-paths' and
'unpack'. How does it really work?
Let's assume that I'll do the same in 'python-build-system.scm'. Can I
reuse 'set-paths' and 'unpack'? Should I write my own functions
instead? How can I determine what environment variables and prefixes
should be used?
I've noticed that 'development/python-modules/generic/default.nix' uses
'easy_install'. Should we use it?
Nikita
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2013-01-23 6:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 6:53 GNU Bazaar doesn't support the GNU build system Nikita Karetnikov
2013-01-18 13:11 ` Ludovic Courtès
2013-01-19 6:19 ` Nikita Karetnikov
2013-01-19 13:46 ` Ludovic Courtès
2013-01-19 22:50 ` Nikita Karetnikov
2013-01-20 14:26 ` Ludovic Courtès
2013-01-23 6:13 ` Nikita Karetnikov [this message]
2013-01-23 15:56 ` Ludovic Courtès
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=874ni8toj4.fsf@karetnikov.org \
--to=nikita@karetnikov.org \
--cc=bug-guix@gnu.org \
--cc=ludo@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).