From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: wip-libreoffice
Date: Fri, 21 Nov 2014 22:25:56 +0100 [thread overview]
Message-ID: <87389cqm8r.fsf@gnu.org> (raw)
In-Reply-To: <20141121173051.GA15388@debian> (Andreas Enge's message of "Fri, 21 Nov 2014 18:30:51 +0100")
Andreas Enge <andreas@enge.fr> skribis:
> On Fri, Nov 21, 2014 at 06:22:23PM +0100, John Darrington wrote:
>> I will do what you suggested. But like you say, it would seem sensible to me, if this entire branch is built
>> only for x86_64, at least for the time being.
>
> I do not see how to do this at the gui level of our hydra install; maybe
> it is not possible. Ludovic?
Right, it’s not possible. build-aux/hydra/gnu-system.scm would need to
be updated to allow that (similar to the ‘subset’ parameter.)
> What you could do maybe is create a dummy package that has supported-system
> set to x86_64-linux only, and have all your other packages inherit from it.
Yeah; actually just put ‘supported-systems’ on LibreOffice itself, since
the other packages may not be that resource hungry.
Thanks,
Ludo’.
prev parent reply other threads:[~2014-11-21 21:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 18:01 wip-libreoffice John Darrington
2014-11-14 18:44 ` wip-libreoffice Andreas Enge
2014-11-14 19:17 ` wip-libreoffice John Darrington
2014-11-18 22:44 ` wip-libreoffice Andreas Enge
2014-11-19 6:16 ` wip-libreoffice John Darrington
2014-11-20 22:56 ` wip-libreoffice Andreas Enge
2014-11-21 8:43 ` wip-libreoffice John Darrington
2014-11-21 9:54 ` wip-libreoffice Andreas Enge
2014-11-21 11:31 ` wip-libreoffice John Darrington
2014-11-21 12:05 ` wip-libreoffice Andreas Enge
2014-11-21 17:22 ` wip-libreoffice John Darrington
2014-11-21 17:30 ` wip-libreoffice Andreas Enge
2014-11-21 21:25 ` Ludovic Courtès [this message]
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=87389cqm8r.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--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.