From: "Sébastien Fabbro" <bicatali@gentoo.org>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] octave forge
Date: Tue, 24 Mar 2009 12:05:49 +0000 [thread overview]
Message-ID: <20090324120549.374426c0@nutmeg.localdomain> (raw)
In-Reply-To: <22644279.post@talk.nabble.com>
On Sunday March 22 atsui wrote:
> markusle wrote:
> >
> > We had a long time
> > ago agreed to go with 3., simply because of the fact that the
> > octave-forge.eclass does most of the work at this point and there
> > is hence no good reason to add a new category to the portage tree
> > which contains many
> > tens of split octave-forge ebuilds that by themselves simply call
> > the eclass
> > and hence don't do anything but waste space.
> >
>
> I've just started following this list, so I was wondering what the
> status of octave-forge is on the overlay? As you know, there might be
> a SoC project to write something to handle the octave packages
> including octave-forge, but I was wondering if there was any
> development in this direction in the last month or so?
The last work has been Markus eclass implementation which is what you
see in the science overlay with git.
> juantxorena wrote:
> >
> > Hopefully GCC-4.3 is going to be stabilized soon. Is there any
> > comment on this?
> >
>
> Does anyone know if this is still a problem?
This is work in progress. Still some packages are not compiling with
gcc-4.3. octave-3 is fine with it. The only worry here is that we want
to have octave-3 stabilize, which is currently being done.
--
Sébastien
next prev parent reply other threads:[~2009-03-24 12:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 16:06 [gentoo-science] octave forge atsui
2009-03-22 22:37 ` Vittorio Giovara
2009-03-24 12:05 ` Sébastien Fabbro [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-04 21:16 Juan Aguado
2009-01-12 16:50 ` Markus Dittrich
2009-01-16 19:50 ` Juan Aguado
2009-02-08 18:06 ` Juan Aguado
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=20090324120549.374426c0@nutmeg.localdomain \
--to=bicatali@gentoo.org \
--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