From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Splitting mkvtoolnix outputs: cycle detected in the references
Date: Wed, 13 Mar 2019 15:55:18 +0100 [thread overview]
Message-ID: <87muly6cyx.fsf@gnu.org> (raw)
In-Reply-To: <87va0u7dle.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Thu, 07 Mar 2019 19:18:21 +0100")
Hi,
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
> I'm trying to split mkvtoolnix-gui (depends on Qt) to a separate "gui" output.
> "out" would only contain the command line tools.
>
> Disabling Qt shrinks the closure size from 1.5+ GB to 277 MB. Pretty
> neat, huh? :)
Yup!
> I naively tried to move mkvtoolnix-gui to the "gui" output:
>
> (add-after 'install 'post-install
> (lambda* (#:key outputs #:allow-other-keys)
> ;; Move the Qt interface to "gui".
> (let ((out (assoc-ref outputs "out"))
> (gui (assoc-ref outputs "gui")))
> (mkdir-p (string-append gui "/bin"))
> (rename-file (string-append out "/bin/mkvtoolnix-gui")
> (string-append gui "/bin/mkvtoolnix-gui")))
> #t))
>
>
> But I get the following error after the
> `compress-documentation' phase:
>
> cycle detected in the references of `/gnu/store/7asc0q7kik1ak463nj8g675hnab7h982-mkvtoolnix-31.0.0-gui'
>
> It's unclear to me why there would be a cycle. Any clue how to
> investigate from there?
This error means that the two outputs, “out” and “gui”, refer to each
other; the daemon does not support that.
To find out where the references come from, you can build with -K, and
then grep -r for one output in the other.
If it turns out to be impossible to remove the cycle, I’d suggest making
a separate package for the GUI.
HTH!
Ludo’.
next prev parent reply other threads:[~2019-03-13 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 18:18 Splitting mkvtoolnix outputs: cycle detected in the references Pierre Neidhardt
2019-03-13 14:55 ` Ludovic Courtès [this message]
2019-03-15 8:20 ` Pierre Neidhardt
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=87muly6cyx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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).