From: Jan Marten Simons <marten@xtal.rwth-aachen.de>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] Fortran90 codes
Date: Mon, 19 Mar 2007 13:38:54 +0100 [thread overview]
Message-ID: <45FE845E.5010007@xtal.rwth-aachen.de> (raw)
In-Reply-To: <45FE687B.90602@gentoo.org>
Donnie Berkholz schrieb:
> Mathias W. wrote:
>> Donnie Berkholz schrieb:
>>> I'm beginning to work on a number of packages that require F90, so I
>>> may
>>> be working to improve the eclass and so forth soon, depending on how
>>> things go. I know we need a tc-getF77() and tc-getF90(), not sure what
>>> other needs we have -- need to research the bugs a bit.
>>>
>>> Current codes for quantum chemistry are on my overlay:
>>> http://dev.gentoo.org/~spyderous/overlay/sci-chemistry/ -- the new ones
>>> are abinit, psi and espresso. Others showing up soon will be schakal,
>>> gabedit, yaehmop.
>>
>> Is there any progress regarding gabedit? I'd like to use this program
>> here with my students. Do you need help with ebuild? Should I try to
>> write one (Though I have very limited experience in this).
>
> No progress, sorry. I forgot I even wrote this, and I haven't had time
> to work on new ebuilds for a while. If you would like to give it a
> try, go for it. Perhaps you'd like to open a new bug once you get an
> initial ebuild and attach it there.
>
> Thanks,
> Donnie
If somebody picks up the work on the eclass it would be good to take F95
into account, too.
Thanks,
Jan
--
gentoo-science@gentoo.org mailing list
prev parent reply other threads:[~2007-03-19 12:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 9:12 [gentoo-science] Fortran90 codes Donnie Berkholz
2006-02-11 14:15 ` M.R. Francis
2006-02-11 18:18 ` M. Edward (Ed) Borasky
2006-02-11 23:03 ` Donnie Berkholz
2007-03-18 17:02 ` Mathias W.
2007-03-19 10:39 ` Donnie Berkholz
2007-03-19 12:38 ` Jan Marten Simons [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=45FE845E.5010007@xtal.rwth-aachen.de \
--to=marten@xtal.rwth-aachen.de \
--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