unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: 宋文武 <iyzsong@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] gnu: libxml2: Build python bindings separately.
Date: Sun, 31 May 2015 12:57:12 -0400	[thread overview]
Message-ID: <876178vg5z.fsf@netris.org> (raw)
In-Reply-To: <87d21hlbsu.fsf@gmail.com> ("宋文武"'s message of "Sun, 31 May 2015 10:29:21 +0800")

宋文武 <iyzsong@gmail.com> writes:

> Mark H Weaver <mhw@netris.org> writes:
>
>> 宋文武 <iyzsong@gmail.com> writes:
>>
>>> * gnu/packages/xml.scm (libxml2)[native-inputs]: Remove python.
>>>   [arguments]: Remove.
>>>   (python-libxml2, python2-libxml): New variables.
>>> ---
>>>  gnu/packages/xml.scm | 53 ++++++++++++++++++++++++++++++----------------------
>>>  1 file changed, 31 insertions(+), 22 deletions(-)
>>>
>>> diff --git a/gnu/packages/xml.scm b/gnu/packages/xml.scm
>>> index a4c81b2..22d4e52 100644
>>> --- a/gnu/packages/xml.scm
>>> +++ b/gnu/packages/xml.scm
>>
>> [...]
>>
>>> +(define-public python2-libxml
>>> +  (package-with-python2 python-libxml2))
>>> +
>>
>> Due to non-obvious complications arising from the fact that xml.scm and
>> python.scm are mutually dependent on each other, we can't use
>> 'package-with-python2' from xml.scm.  For now, I suggest moving it to
>> python.scm, where all other uses of 'package-with-python2' are currently
>> located.
>>
>> For an explanation, see:
>>
>> https://lists.gnu.org/archive/html/guix-devel/2014-12/msg00355.html
> Thanks for explainging, but when I put it into python.scm,
> I got "Unbound variable: libxml2" when running:
>   $ ./pre-inst-env guix package -i python2-libxml
> or:
>   $ make
> but not:
>   $ ./pre-inst-env guix build python2-libxml
>
> Any ideas? Thanks!

It turns out that 'package-with-python2' is no longer exported from
(gnu packages python), but rather from (guix build-system python) which
is not part of any cycles, so it is now okay to use 'package-with-python2'
from other modules.

In fact, because of the (inherit libxml2) in 'python-libxml2', these
packages should be in xml.scm, right where you had put them -- or at
least not in any other module that shares a cycle with xml.scm -- so
please disregard my suggestion that they should be moved.

However, I just noticed one minor mispelling: the variable should be
named 'python2-libxml2', not 'python2-libxml'.

    Thanks!
      Mark

  reply	other threads:[~2015-05-31 16:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-30  9:12 [PATCH 1/2] gnu: libxml2: Update to 2.9.2 宋文武
2015-05-30  9:12 ` [PATCH 2/2] gnu: libxml2: Build python bindings separately 宋文武
2015-05-30 16:07   ` Mark H Weaver
2015-05-31  2:29     ` 宋文武
2015-05-31 16:57       ` Mark H Weaver [this message]
2015-06-01  1:01         ` 宋文武
2015-05-30 16:00 ` [PATCH 1/2] gnu: libxml2: Update to 2.9.2 Mark H Weaver
2015-05-31  2:20   ` 宋文武

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=876178vg5z.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=iyzsong@gmail.com \
    /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).