From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: bug-guix@gnu.org
Subject: Re: GNU Bazaar doesn't support the GNU build system
Date: Sun, 20 Jan 2013 15:26:09 +0100 [thread overview]
Message-ID: <871udgvsla.fsf@gnu.org> (raw)
In-Reply-To: <87mww4bxdj.fsf@karetnikov.org> (Nikita Karetnikov's message of "Sat, 19 Jan 2013 17:50:25 -0500")
Nikita Karetnikov <nikita@karetnikov.org> skribis:
> AFAICT, the '#:phases' keyword can't be used because it requires
> '%standard-phases'. There is also '#:builder', but I haven't found a
> way to use it.
So, #:phases is a keyword parameter recognized by ‘gnu-build-system’.
It lets you introduce, remove, or modify the normal build “phases” (see
gnu-build-system.scm). This is useful when you just have to introduce
small changes, and when the package’s build system is similar to the GNU
build system—i.e., use something close to ./configure && make && make
install (info "(guix) Defining Packages").
In the case of Python packages, the right thing would be to define a
‘python-build-system’. You’d add a (guix build-system python) module
that exports ‘python-build-system’; packages would use it as the value
of their ‘build-system’ field, which would mean that they get built,
installed, and tested via the ‘python setup.py install’ etc. commands.
This way, many/most Python packages would need little or no
customization once they use ‘python-build-system’.
So that’s the idea. You could check
development/python-modules/generic/default.nix in Nixpkgs to see how
it’s done there.
I realize this is a bit more involved than “just” packaging the thing,
but it will be useful in the long run.
WDYT?
Ludo’.
next prev parent reply other threads:[~2013-01-20 14:26 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 [this message]
2013-01-23 6:13 ` Nikita Karetnikov
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=871udgvsla.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guix@gnu.org \
--cc=nikita@karetnikov.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).