#1153 Factor out grid external managers
Metadata
Property | Value |
---|---|
Reported by | Andreas Lauser (andreas.lauser@iws.uni-stuttgart.de) |
Reported at | Jul 13, 2012 10:17 |
Type | Feature Request |
Version | 2.2 |
Operating System | Unspecified / All |
Last edited by | Oliver Sander (oliver.sander@tu-dresden.de) |
Last edited at | Mar 9, 2015 17:26 |
Closed by | Oliver Sander (oliver.sander@tu-dresden.de) |
Closed at | Mar 9, 2015 17:26 |
Closed in version | Unknown |
Resolution | Won't implement |
Comment |
Description
I've toyed with the idea of factoring the external grid managers out of dune-grid (while probably still leaving them core modules). The ones I'm thinking about are UGGrid, ALUGrid and ALBERTA. This would have a few advantages:
- Easier packaging: no need to strip out these grid managers when creating packages. Also, these grid managers could also be bundled with their libraries (at least if there are no "hard" licensing restrictions), and provided in external repositories (or debian's contrib repositories).
- Possibility to specify dependencies: dunecontrol modules can add Depends: or Suggests: directives in their dune.module file
- The same dune-grid core library could be used for the MPI enabled and disabled case. Currently it always requires recompiling when switching from sequential to parallel grids. (I'm not so sure about this point, but I'm sure that it would be much easier if dune-grid would not host the external grid managers.
For ALUGrid, the DUNE grid manager could also be included directly in the tarball, so from a user perspective, this would add no overhead.
I eager for the discussion...