all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Add package definition for GNU XaoS.
Date: Wed, 30 Dec 2015 16:51:42 +0100	[thread overview]
Message-ID: <87y4ccszn5.fsf@gnu.org> (raw)
In-Reply-To: <87egedmtxt.fsf@gmail.com> (Alex Kost's message of "Wed, 23 Dec 2015 11:48:46 +0300")

Alex Kost <alezost@gmail.com> skribis:

> Alex Kost (2015-12-21 15:42 +0300) wrote:
>
>> Fabian Harfert (2015-12-15 23:02 +0300) wrote:
>>
>> [...]
>>> @@ -53,6 +54,7 @@
>>>    #:use-module (gnu packages ghostscript)
>>>    #:use-module (gnu packages glib)
>>>    #:use-module (gnu packages gtk)
>>> +  #:use-module (gnu packages image)
>>
>> Our (gnu packages image) module uses (gnu packages maths).  I wouldn't
>> add this circularity, I think it was better to have xaos in a separate
>> module.  But actually I don't know if it's a real issue and what our
>> policy on such things is.  I hope more experienced guix/guile people
>> will tell if we should avoid such circularities.
>
> Sorry for bumping, just to prevent this package from burying in ML.
>
> Originally Fabian sent a patch for separate "xaos.scm" file.  Then
> Andreas suggested to move it to "maths.scm".  But this will lead to the
> mentioned circularity:
>   (gnu packages image) already uses (gnu packages maths)
> and after this patch:
>   (gnu packages maths) will use (gnu packages image).
>
> Is it OK to leave it like this, or should 'xaos' be left in a
> separate file?

It’s OK to leave it as is.

Module circularity are not a problem, unless there are circular
*top-level* references.

That is, if maths.scm does, say:

  (define foo libpng)

and image.scm does:

  (define bar lapack)

then we have a problem.

Ludo’.

  reply	other threads:[~2015-12-30 15:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-15 19:51 [PATCH] Add package definition for GNU XaoS Fabian Harfert
2015-12-15 20:02 ` Fabian Harfert
2015-12-21 12:42   ` Alex Kost
2015-12-21 13:35     ` Ludovic Courtès
2015-12-23  8:48     ` Alex Kost
2015-12-30 15:51       ` Ludovic Courtès [this message]
2015-12-31  8:35         ` Alex Kost
2016-01-01 15:56           ` Ludovic Courtès
2015-12-31  8:35     ` Alex Kost
  -- strict thread matches above, loose matches on Subject: below --
2015-12-14 21:01 Fabian Harfert
2015-12-14 22:58 ` Leo Famulari
2015-12-15 19:24   ` Alex Kost
2015-12-15 20:45     ` Leo Famulari
2015-12-15  7:22 ` Andreas Enge
2015-12-15 19:23   ` Alex Kost
2015-12-16  1:48     ` Andreas Enge
2015-12-16 17:38       ` Fabian Harfert
2015-12-19  2:24         ` Mark H Weaver
2015-12-15 19:24 ` Alex Kost
2015-12-16  1:09   ` Leo Famulari

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y4ccszn5.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alezost@gmail.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.