unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Specifying and build output separately?
Date: Mon, 17 Oct 2016 10:55:48 +0200	[thread overview]
Message-ID: <87y41ne4mj.fsf@gnu.org> (raw)
In-Reply-To: <118ccdd8-3b7f-2b35-5f5e-69375c1a4565@crazy-compilers.com> (Hartmut Goebel's message of "Sat, 15 Oct 2016 10:06:34 +0200")

Hello,

Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:

> we have several cyclic dependencies due to e.g. packages depending on
> each other only for building the documentation. Examples are numpy and
> matpltlib.
>
> So I wonder it it would be possible to to something like this:
>
> (define-public numpy:doc
>   (inherit numpy)
>   (name "numpy:doc")
>   (outputs "doc")
>   (inputs … matplotlib …)
>   (… modify-phases …))

Making the documentation a separate package, instead of a separate
output, is of course doable and it could help address the circular
reference issue.

Currently the approach used for numpy is a different one: there’s a
“bootstrap” package lacking documentation that is used as input to the
final package, which has an extra “doc” output.

I prefer this approach over what you propose because it’s more
consistent with what we usually do, which is to have doc in a “doc”
output rather than in a separate package.

Thanks,
Ludo’.

  reply	other threads:[~2016-10-17  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-15  8:06 Specifying and build output separately? Hartmut Goebel
2016-10-17  8:55 ` Ludovic Courtès [this message]
2016-10-17  9:06   ` Hartmut Goebel
2016-10-17 14:54     ` 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=87y41ne4mj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.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).