public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: Radice David <david.e.pi.3.14@gmail.com>
To: gentoo-science@lists.gentoo.org
Subject: [gentoo-science] Re: Empi, should it be in the science overlay?
Date: Wed, 14 May 2008 20:54:31 +0200	[thread overview]
Message-ID: <1210791271.6604.35.camel@gentoo> (raw)
In-Reply-To: <20080226154538.GC3622@mejis.cold-front>

Hi,
I am playing with it right now, but I had to patch it this way to make
it work with my /etc/portage/package.* directories:

--- empi.old	2008-05-14 19:35:00.000000000 +0200
+++ empi.new	2008-05-14 19:39:30.000000000 +0200
@@ -106,7 +106,7 @@
         fi
 
         if ! grep "[>=<]*${imp}/${atom[1]}" ${gfiles} &>/dev/null; then
-            grep "[>=<]*${atom[0]}/${atom[1]}" ${gfiles} 2>/dev/null \
+            grep -h "[>=<]*${atom[0]}/${atom[1]}" ${gfiles} 2>/dev/null \
                 | sed "s,${atom[0]},${imp}," \
             | while read line; do
                echo "${line}" >> ${f}

otherwise grep will produce a wrong output because it will prefix the
file name before the found expression and something like this is put
inside the keyword file:

/etc/portage/package.keywords/base:mpi-test/openmpi ~x86

Thanks,
David.

On Tue, 2008-02-26 at 10:45 -0500, Justin Bronder wrote:
> I've been spending the majority of my Gentoo-related time working on a
> solution to bug 44132 [1], basically, trying to find a way to gracefully
> handle multiple installs of various MPI implementations at the same time in
> Gentoo.  Theres more information about the solution in my devspace [2], but
> a quick summary is that there is a new package (empi) that is much like
> crossdev, a new eselect module for empi, and a new eclass that handles both
> mpi implementations and packages depending on mpi.
> 
> So, I think I have pushed this work far enough along for it to actually be
> somewhat officially offered.  My question then, is where should this be
> located?  There are several mpi packages in the science overlay already, so
> should I push this work to there, or would it be more appropriate to make a
> new overlay specifically for hp-cluster?
> 
> Future work related to this project will be getting all mpi implementations
> and dependant packages converted in the same overlay before bringing it up on
> -dev for discussion about inclusion into the main tree.
> 
> I have no real preference either way, but the science team does already have
> an overlay :)  Let me know what you think.
> 
> [1] https://bugs.gentoo.org/show_bug.cgi?id=44132
> [2] http://dev.gentoo.org/~jsbronder/README.empi.txt
> 

-- 
gentoo-science@lists.gentoo.org mailing list



  parent reply	other threads:[~2008-05-14 18:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 15:45 [gentoo-science] Empi, should it be in the science overlay? Justin Bronder
2008-02-26 15:57 ` Alexey Shvetsov
2008-02-26 17:44 ` Donnie Berkholz
2008-02-26 18:21   ` [gentoo-science] " Justin Bronder
2008-02-27  9:18     ` Alexey Shvetsov
2008-02-28 16:26 ` Justin Bronder
2008-05-14 18:54 ` Radice David [this message]
2008-05-15  2:01   ` Justin Bronder

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=1210791271.6604.35.camel@gentoo \
    --to=david.e.pi.3.14@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