From: atsui <alextsui05@gmail.com>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] octave forge
Date: Sun, 22 Mar 2009 09:06:27 -0700 (PDT) [thread overview]
Message-ID: <22644279.post@talk.nabble.com> (raw)
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?
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?
Thanks,
--Alex
--
View this message in context: http://www.nabble.com/octave-forge-tp21281356p22644279.html
Sent from the gentoo-science mailing list archive at Nabble.com.
next reply other threads:[~2009-03-22 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 16:06 atsui [this message]
2009-03-22 22:37 ` [gentoo-science] octave forge Vittorio Giovara
2009-03-24 12:05 ` Sébastien Fabbro
-- 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=22644279.post@talk.nabble.com \
--to=alextsui05@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