[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Question related to outputs
From: |
Pjotr Prins |
Subject: |
Re: Question related to outputs |
Date: |
Wed, 15 Mar 2017 20:32:03 +0000 |
User-agent: |
Mutt/1.6.2 (2016-07-01) |
On Wed, Mar 15, 2017 at 05:24:47PM +0100, Ludovic Courtès wrote:
> So if your package declares “out” and “debug” as its outputs, it must
> always produce both. Then users can choose to install only one or both,
> but that’s a different issue.
That clarifies that :). Both get built.
> For instance, ‘glibc’ always produces both “out” and “debug”, but you
> can choose which one to install.
>
> > In gnu/packages/python.scm:L268
> >
> > (let ((out (assoc-ref outputs "out"))
> > (tk (assoc-ref outputs "tk")))
> > (when tk
> > (match (find-files out "tkinter.*\\.so")
> > ...
> >
> > looks faulty to me as tk always expands to an outputs path.
>
> It can also be #f in the case of python-minimal.
I'll check on that one.
So, to have different build procedures for the same package I best
define different packages and inherit? Rather than define different
outputs - it just appeared natural to me ;).
Pj.