From: "François Bissey" <frp.bissey@gmail.com>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] [sage-on-gentoo] Cannot install sage-doc: insufficient memory
Date: Thu, 20 Nov 2014 11:00:10 +1300 [thread overview]
Message-ID: <32944813.ujtKSMfopY@qcd-nzi3> (raw)
In-Reply-To: <20140923143503.30dd6230aa79574f312c7cdd@ukr.net>
As of today we have sage-doc and sage-doc-bin in the overlay for sage 6.4. By
default sage-doc-bin is the only one keyworded.
For development/beta/rc work (sage*-9999 ebuilds) only sage-doc is the only
possibility as upstream do not provide pre-built doc for these.
There is usually a lag between upstream release and the availability of
pre-build doc, so early adopters will always have to build their own
docs.
Making building the doc the default was motivated by the failure by sage
upstream to provide pre-build doc for a long time for sage 6.2.
Francois
On Tue, 23 Sep 2014 14:35:03 v_2e@ukr.net wrote:
> On Tue, 23 Sep 2014 21:49:28 +1200
>
> François Bissey <frp.bissey@gmail.com> wrote:
> > I am definitely giving some thought on that but nothing concrete
> > so far. Upstream is not managing it at all so any solution will be our
> > own work.
>
> And if I understand correctly, sage depends on sage-doc, so the
> sage-doc is not even an optional package. Am I right?
>
>
> -----
> <v_2e@ukr.net>
next prev parent reply other threads:[~2014-11-19 22:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-20 9:56 [gentoo-science] [sage-on-gentoo] Cannot install sage-doc: insufficient memory v_2e
2014-09-20 9:57 ` François Bissey
2014-09-20 10:02 ` v_2e
2014-09-20 10:01 ` François Bissey
2014-09-20 21:55 ` v_2e
2014-09-21 21:52 ` François Bissey
2014-09-23 7:51 ` v_2e
2014-09-23 8:51 ` François Bissey
2014-09-23 9:48 ` v_2e
2014-09-23 9:49 ` François Bissey
2014-09-23 11:35 ` v_2e
2014-09-23 11:38 ` François Bissey
2014-11-19 22:00 ` François Bissey [this message]
2014-09-25 0:59 ` François Bissey
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=32944813.ujtKSMfopY@qcd-nzi3 \
--to=frp.bissey@gmail.com \
--cc=gentoo-science@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox