1 |
On 10:45 Tue 26 Feb , Justin Bronder wrote: |
2 |
> I've been spending the majority of my Gentoo-related time working on a |
3 |
> solution to bug 44132 [1], basically, trying to find a way to gracefully |
4 |
> handle multiple installs of various MPI implementations at the same time in |
5 |
> Gentoo. Theres more information about the solution in my devspace [2], but |
6 |
> a quick summary is that there is a new package (empi) that is much like |
7 |
> crossdev, a new eselect module for empi, and a new eclass that handles both |
8 |
> mpi implementations and packages depending on mpi. |
9 |
|
10 |
Is it enough like crossdev enough to share code, with perhaps a bit of |
11 |
abstraction? Maintaining the same thing twice is rarely a good idea... |
12 |
|
13 |
> So, I think I have pushed this work far enough along for it to actually be |
14 |
> somewhat officially offered. My question then, is where should this be |
15 |
> located? There are several mpi packages in the science overlay already, so |
16 |
> should I push this work to there, or would it be more appropriate to make a |
17 |
> new overlay specifically for hp-cluster? |
18 |
> |
19 |
> Future work related to this project will be getting all mpi implementations |
20 |
> and dependant packages converted in the same overlay before bringing it up on |
21 |
> -dev for discussion about inclusion into the main tree. |
22 |
> |
23 |
> I have no real preference either way, but the science team does already have |
24 |
> an overlay :) Let me know what you think. |
25 |
|
26 |
Seems like people already committing cluster stuff to the sci overlay |
27 |
could help; maybe they'll port packages, fix bugs, etc. With a new |
28 |
overlay, we'd have to start from scratch, and I don't really see the |
29 |
point. |
30 |
|
31 |
Thanks, |
32 |
Donnie |
33 |
-- |
34 |
gentoo-science@l.g.o mailing list |