.codechecker/config.json

+{
+  "analyze": [
+    "--disable", "default",
+    "--analyzers=clang-tidy",
+    "--file=*/dune-common/*.cc",
+    "--skip", ".codechecker/skipfile",
+    "--disable", "clang-diagnostic-deprecated-copy",
+    "--disable", "clang-diagnostic-unused"
+  ],
+  "parse": [
+    "--file=*/dune-common/*"
+  ]
+}

.codechecker/config.json.license

+SPDX-FileCopyrightInfo: Copyright © DUNE Project contributors, see file LICENSE.md in module root
+SPDX-License-Identifier: LicenseRef-GPL-2.0-only-with-DUNE-exception

.codechecker/skipfile

+-*/densematrixassignmenttest.cc
+-*/genericiterator_compile_fail.cc
+-*/check_fvector_size_fail.cc
+-*/assertandreturntest.cc

.codechecker/skipfile.license

+SPDX-FileCopyrightInfo: Copyright © DUNE Project contributors, see file LICENSE.md in module root
+SPDX-License-Identifier: LicenseRef-GPL-2.0-only-with-DUNE-exception

.gitignore

-Makefile
-Makefile.in
-config.guess
-config.h.in
-config.log
-config.status
-config.h
-config.lt
-config.sub
-configure
-configure
-aclocal.m4
-autom4te.cache
-depcomp
-install-sh
-missing
-mkinstalldirs
-libtool
-dune-common.pc
-semantic.cache
-configure.lineno
-stamp-h1
-dune-common-*.tar.gz
-dune-common-?.?
-ltmain.sh
-.libs/
-.deps/
-*.la
-*.o
-*.lo
-compile
-test-driver
-dependencies.m4
-dune.css
-build-cmake/
+# SPDX-FileCopyrightInfo: Copyright © DUNE Project contributors, see file LICENSE.md in module root
+# SPDX-License-Identifier: LicenseRef-GPL-2.0-only-with-DUNE-exception
+
+# ignore all build folders
+/build*/
+# ignore backup files
 *~
+# ignore Python files
+*.pyc
+# ignore files generated during python setup.py sdist
+MANIFEST
+_skbuild/
+dist
+*.egg-info/
+# ignore macOS filesystem
+.DS_Store
+

.gitlab-ci.yml

+# SPDX-FileCopyrightInfo: Copyright © DUNE Project contributors, see file LICENSE.md in module root
+# SPDX-License-Identifier: LicenseRef-GPL-2.0-only-with-DUNE-exception
+
+---
+include:
+  - remote: 'https://gitlab.dune-project.org/core/ci-config/raw/master/config/common/master.yml'
+  - remote: 'https://gitlab.dune-project.org/core/ci-config/raw/master/jobs/common/master.yml'
+
+before_script:
+  - . /duneci/bin/duneci-init-job
+
+variables:
+  DUNECI_TEST_LABELS: quick
+  DUNE_TEST_EXPECTED_VC_IMPLEMENTATION: SSE2
+  PIP_DEFAULT_TIMEOUT: 0
+  DUNE_LOG_LEVEL:     DEBUG
+
+debian:11 gcc-10-20-expensive:
+  extends: .common
+  # This image has Vc
+  image: registry.dune-project.org/docker/ci/debian:11
+  # allow expensive tests
+  variables:
+    DUNECI_CXXFLAGS: -mavx
+    DUNECI_TEST_LABELS: ""
+    DUNECI_TOOLCHAIN: gcc-10-20
+    DUNECI_CMAKE_FLAGS: '-DDUNE_ENABLE_PYTHONMODULE_PRECOMPILE:BOOL=TRUE'
+    DUNE_TEST_EXPECTED_VC_IMPLEMENTATION: AVX
+  # require AVX to properly test Vc
+  tags: [duneci, "iset:avx"]
+  # allowed to fail to e.g. do no hold up a merge when a runner supporting avx
+  # is unavailable
+  allow_failure: true
+
+core-modules-test:
+  stage: downstream
+  inherit:
+    variables: false # do not inherit global variables
+  variables:
+    CI_BUILD_REF_NAME: $CI_COMMIT_REF_NAME
+    DUNECI_TEST_LABELS: ""
+  trigger:
+    project: infrastructure/dune-nightly-test
+    branch: core
+    strategy: depend
+  rules:
+    - when: manual
+      allow_failure: false
+
+full-system-test:
+  stage: downstream
+  inherit:
+    variables: false # do not inherit global variables
+  variables:
+    CI_BUILD_REF_NAME: $CI_COMMIT_REF_NAME
+    DUNECI_TEST_LABELS: ""
+  trigger:
+    project: infrastructure/dune-nightly-test
+    branch: master
+    strategy: depend
+  rules:
+    - when: manual
+      allow_failure: true
+
+# Check for spelling mistakes in text
+code-spelling-check:
+  stage: .pre
+  tags: [duneci]
+  image: registry.dune-project.org/docker/ci/debian:11
+  script:
+  - codespell
+    --ignore-words-list te,inout,incrementall,iif,\trun,referr,ba
+    --skip pybind11
+
+reuse:
+  stage: .pre
+  image:
+    name: docker.io/fsfe/reuse:latest
+    entrypoint: [""]
+  tags: [duneci]
+  before_script: ""
+  script:
+    - reuse lint

.mailmap

+# SPDX-FileCopyrightInfo: Copyright © DUNE Project contributors, see file LICENSE.md in module root
+# SPDX-License-Identifier: LicenseRef-GPL-2.0-only-with-DUNE-exception
+
 Benjamin Bykowski <benjamin.bykowski@rwth-aachen.de> Convex Function <329364@wright.mathepool.rwth-aachen.de>
 

.reuse/dep5

+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: dune-common
+Upstream-Contact: Dune Developers <dune-devel@lists.dune-project.org>
+Source: https://dune-project.org
+
+Files:
+  dune/python/pybind11/*.h
+  dune/python/pybind11/_version.py
+Copyright:
+  Copyright (c) 2016 Wenzel Jakob <wenzel.jakob@epfl.ch>
+  Copyright (c) 2016 Trent Houliston <trent@houliston.me>
+  Copyright (c) 2016 Klemens Morgenstern <klemens.morgenstern@ed-chemnitz.de>
+  Copyright (c) 2016 Andreas Dedner <a.s.dedner@warwick.ac.uk>
+  Copyright (c) 2016 Martin Nolte <nolte@mathematik.uni-freiburg.de>
+  Copyright (c) 2017 Henry F. Schreiner
+  Copyright (c) 2016 Sergey Lyskov and Wenzel Jakob
+License: BSD-3-Clause

CHANGELOG.md

+<!--
+SPDX-FileCopyrightInfo: Copyright © DUNE Project contributors, see file LICENSE.md in module root
+SPDX-License-Identifier: LicenseRef-GPL-2.0-only-with-DUNE-exception
+-->
+
+# Master (will become release 2.11)
+
+## Build system: Changelog
+
+- Propagate dependencies of `dune-common` when consumed. This means that a CMake project may find
+  `dune-common` and consume the `Dune::Common` target without the need of the dune build system.
+
+- Change the way include directories are set in dune projects. OLD behavior: use `include_directories`
+  in `dune_project` to set include dirs for the current project. NEW behavior: Provide a utility
+  `dune_default_include_directories` to set include dirs on targets manually. Which behavior to
+  activate can be decided in each module by using the new dune policy `DP_DEFAULT_INCLUDE_DIRS`, which can be set
+  to `OLD` or `NEW` correspondingly.
+
+- The CMake function `dune_target_enable_all_packages` can now handle Interface libraries too.
+
+- Add a module-specific CMake target `build_<module>_tests` to compile only tests
+  associated to a specific `<module>`. Additionally, add the `<module>`-name as
+  `LABEL` property to all tests created with `dune_add_tests` in that module. This
+  allows to run these tests with `ctest -L <module>`.
+
+- Change the behavior of `dune_add_test`: Do not add all package flags automatically. This new behavior
+  can be controlled by the new Dune policy `DP_TEST_ADD_ALL_FLAGS`.
+
+## C++: Changelog
+
+- `Dune::IteratorRange` now supports different types for begin and end iterator
+  to model C++20's sentinel terminated ranges.
+
+- Add preprocessor macro `DUNE_FORCE_INLINE` as a portable attribute to force inlining of functions (if supported).
+
+- Add `bit_width` and `countl_zero` overloads for `bigunsignedint` objects.
+
+- `DUNE_THROW` no longer prevents functions from being used in `constexpr` contexts,
+  as long the exception is not thrown. As a sideproduct, the macros now
+  also supports the syntax `DUNE_THROW(ExceptionType, a << b) << c << d` and
+  `DUNE_THROW(ExceptionType) << a << b`.
+
+- Add `constexpr` qualifiers to many member functions of `DenseMatrix`, `FieldMatrix`, `DenseVector`,
+  `FieldVector`, `ForwardIteratorFacade`, `BidirectionalIteratorFacade`, `RandomAccessIteratorFacade`,
+  `TupleVector` and to the function `range`.
+
+- Add concepts `Std::three_way_comparable` and `Std::three_way_comparable_with` as well as an
+  algorithm `Std::lexicographical_compare_three_way` to provide library utilities for the `<=>`
+  comparison operator.
+
+- Add deduction guides to `TupleVector` analogous to `std::tuple`.
+
+- Add concept definition `Std::indirectly_copyable` to constrain the `DenseMatrixAssigner`.
+
+- Add concept definition `Concept::Number` to represent scalar number types in containers.
+
+- Add the macro `DUNE_ASSUME` for portable compiler assumption.
+
+## C++: Deprecations and removals
+
+- Deprecate the utility `integerSequenceEntry` in favour of the shorter `get` from `integersequence.hh`.
+
+## Python: Changelog
+
+- the `sdist` tar ball name should not use `-` (see PEP 625) so use `_` instead
+  `pip install dune-common` will still work as expected but `pip list` will
+  now show `dune_common` so the output of `pip list` is parsed anywhere
+  this is a breaking change.
+
+# Release 2.10
+
+## Dependencies
+In order to build the DUNE core modules you need at least the following software:
+
+- C++ compilers LLVM Clang >= 10 or GCC g++ >= 9
+- CMake >= 3.16
+- Optional: pkg-config to find other optional dependencies
+- The Python bindings require at least Python 3.7 or higher. This is now enforced
+  through CMake. The bindings are disabled prompting the user with a message containing
+  the reason if no suitable Python version is found.
+
+
+## C++: Changelog
+
+- Fix bug where `AlignedNumber` could not check if placement `new` alignment is correct.
+
+- `TupleVector` now implements the standard protocol for tuple-like types.
+
+- There is a new base class `IteratorFacade` that unifies `ForwardIteratorFacade`,
+  `BidirectionalIteratorFacade`, `RandomAccessIteratorFacade` by making the iterator
+  category a template. Furthermore the new `IteratorFacade`  class allows to specify
+  a `pointer` type other than `value_type*` to support proxy-iterators.
+  The old facade classes remain unchanged for backward compatibility reasons.
+
+- Add utilities `Std::span`, `Std::mdspan`, `Std::mdarray` and all its related classes into the `Dune::Std` namespace
+  for working with multidimensional arrays. See core/dune-common!1334 for further details.
+
+- The construction of `FiedlMatrix` and `FieldVector` from `std::initializer_list`
+  is now `constexpr`.
+
+- Add concepts directory `dune/common/concepts/` and some fundamental concept definitions using
+  c++20-concepts. Those concepts are still experimental and are marked with the new `doxygen`
+  command `\experimental`. Additionally, the preprocessor constant `DUNE_ENABLE_CONCEPTS` is
+  provided when including `dune/common/concepts.hh` that tells whether the library and compiler
+  understand the new c++20-concepts and the concept definitions can be used. This constant can also
+  be set manually as a compilerflag to enforce enabling or disabling these features.
+
+- Two concept definitions are added: `Dune::Concept::Hashable` and
+  `Dune::Concept::[RandomAccess]Container` in `dune/common/concepts/` directory.
+
+- Add user-defined literals `_ic`, `_uc` and `_sc` to represent integral constants.
+
+- Add "hybrid" functors for basic math operations with integral constant arguments, i.e.,
+  `Hybrid::max`, `Hybrid::min`, `Hybrid::plus`, `Hybrid::minus`, and `Hybrid::equal_to`. Operations
+  between two integral constants result in an integral constant, whereas operations with at least
+  one non integral constant argument is performed on the underlying value type.
+
+- Make `filledArray` compatible with non-default-constructble types.
+
+- Add utility `CopyableOptional` that allows to wrap types that are copy constructible but not
+  copy assignable and provide assignment operations based on the constructors.
+
+- Added the methods `checkThrow`,`requireThrow` and the corresponding `checkNoThrow`,
+  `requireNoThrow` to the `Dune::TestSuite` to test for throwing and no throwing of exceptions.
+
+- Add the utility `IsCompileTimeConstant` to check for integral constants and anything with
+  the same interface.
+
+- Add dedicated includes `dune/common/metis.hh` for METIS and `dune/common/parallel/parmetis.hh`
+  for ParMETIS to be used instead of the direct includes `metis.h` and `parmetis.h`.
+
+- Add utilities and algorithms to work with `std::integer_sequences`.
+
+- Fixed MPI implementation of `Communication::isend`.
+
+- Move special MPI-related compile flags, like `MPI_NO_CPPBIND`, from `config.h` into
+  the cmake utiltiy `add_dune_mpi_flags` and the related global package registration.
+
+- Add new utility type `IndexedIterator` that extends a given iterator by an `index()`
+  method returning a traversal index.
+
+- Add a macro `DUNE_NO_UNIQUE_ADDRESS` that expands to the attribute `[[no_unique_address]]`
+  or something similar, if supported by the compiler.
+
+## C++: Deprecations and removals
+
+- Remove deprecated macros `DUNE_VERSION_NEWER` and `DUNE_VERSION_NEWER_REV`, use `DUNE_VERSION_GTE`
+  and `DUNE_VERSION_GTE_REV` instead. There was no deprecation compiler warning.
+
+- The deprecated header `dune/common/function.hh` has been removed. Use C++ function
+  objects and `std::function` stuff instead!
+
+- The deprecated header `dune/common/std/utility.hh` has been removed. Use `<utility>`
+  instead.
+
+- The deprecated header `dune/common/std/variant.hh` has been removed. Use `<variant>`
+  instead.
+
+- The deprecated header `dune/common/to_unique_ptr.hh` has been removed. Use
+  `std::unique_ptr` or `std::shared_ptr` instead.
+
+- Deprecated `conjunction`, `disjunction`, and `negation` have been removed. Instead,
+  use the structs from `<type_traits>` introduced with C++17.
+
+- Remove deprecated `dune/common/std/apply.hh`, use `std::apply` instead.
+
+- Deprecated the file `dune/common/assertandreturn.hh` and the contained utility
+  `DUNE_ASSERT_AND_RETURN`. Use `assert()` macro directly in `constexpr` functions.
+
+- Remove deprecated header `power.hh`. Use `Dune::power` from `math.hh` instead.
+
+- Deprecate class `SizeOf`. Use `sizeof...` instead.
+
+- Deprecate header `dune/common/keywords.hh` and the provided macros
+  `DUNE_GENERALIZED_CONSTEXPR` and `DUNE_INLINE_VARIABLE`. Use the key words directly.
+
+- Remove deprecated header `dune/python/common/numpycommdatahandle.hh`. Use
+  `dune/python/grid/numpycommdatahandle.hh` instead.
+
+- Remove in `dune/python/common/dimrange.hh` the `DimRange` specializations for
+  dune-typetree and dune-functions types. Those are moved to dune-functions.
+
+- Deprecated `Hybrid::equals`. Use `Hybrid::equal_to` instead.
+
+- The preprocessor constant `HAVE_UMFPACK` is deprecated. Use `HAVE_SUITESPARSE_UMFPACK` instead.
+
+## Python: Changelog
+
+- Python: Add `TupleVector` Python bindings
+
+- Python: The function `cppType` now support Python tuples, which are converted to the C++ type `std::tuple`
+
+- Python: Add a dump/load functions to dune.common.pickle which add support
+  for storing and recreating the JIT generated modules required for the
+  pickling of dune objects to work. In addition a class for writing time
+  series of pickled data is provided.
+
+- Python: Add a new argument class to the generator to add pickling support.
+  The approach is similar to adding extra constructors or methods.
+
+- Python: Add a new command to `dune.__main__` to compile existing modules
+  in parallel, e.g., python -m dune make -j8 hierarchicalgrid
+  Add the option to both 'remove' and 'make' commands to read
+  module list from a file.
+
+## Build system: Changelog
+
+- Add a `REQUIRED` parameter to `dune_python_configure_bindings`. If set to
+  `TRUE` the functions throws an error instead of a warning if the package
+  setup fails. The default behavior (or setting `REQUIRE` to `FALSE`) is to
+  show the warning during configuration and to continue.
+
+- Dune package dependencies are now transitively resolved at `find_package(<dune-module>)` calls instead of waiting
+  until the call to `dune_project()`. For example, a CMake call to `find_package(dune-grid)` will transitively
+  find the dune packages `dune-common`, `dune-geometry` and (if available) `dune-uggrid`. Note that the targets
+  provided by those found modules are still being set up at the `dune_project()` call.
+
+- Documentation files in `doc/buildsystem/${ModuleName}.rst` are now only copied.
+  Previously, they were configured through the CMake function `configure_file()`
+  as a cmake template file.
+
+- Try to find SuiteSparse during configuration.
+
+- The function `dune_add_library(<lib> ...)` now requires to provide `EXPORT_NAME` or `NO_EXPORT`.
+  Moreover, a namespace can be specified via the argument `NAMESPACE` which defaults to `Dune::` and is prepended to the export name.
+  We recommend to choose an export name with a camel title case matching your
+  library name (e.g., `Common`, `ISTL`, and `MultiDomainGrid` will be exported as
+  `Dune::Common`, `Dune::ISTL`, and `Dune::MultiDomainGrid`).
+  _Warning:_ Both `<lib>` and `Dune::${EXPORT_NAME}` are currently exported. Keep in mind that:
+   * Libraries that _consume_ `Dune::${EXPORT_NAME}` will only be forward compatible with Dune 2.10.
+   * Libraries that _consume_ `<lib>` will be supported until compatibility with Dune 2.9 is not required anymore.
+
+- Generation of `config.h` is overhauled and split in a public and a private config file. Only
+  the public file is installed and consumed by down-stream modules. For compatibility, the
+  old single file is created, too.
+
+- The CMake macro `finalize_dune_project` no longer has an optional argument, a config file is
+  always created.
+
+- Do not overwrite the `add_test` cmake function with an error message.
+
+- Setting the minimal c++ standard in cmake is now done by a cmake feature-requirement
+  `cxx_std_17` on the `dunecommon` library target. This requirement is propagated to all
+  other modules by linking against `dunecommon`.
+
+- We have changed the way optional dependencies are activated in the build-system internally.
+  The cmake macros `add_dune_xy_flags` do not set the compiler flag `-DENABLE_XY=1` anymore, but instead
+  set directly the flag `-DHAVE_XY=1`. Neither `ENABLE_XY` nor `HAVE_XY` should be modified manually
+  by the user. Since the `HAVE_XY` flag is now set as a compiler flag, it is not included in the
+  `config.h` files anymore.
+
+- Add a policy system to smoothly change behavior in the build-system. This follows the cmake policy
+  system but uses own IDs and is connected to dune module version instead of cmake versions.
+
+- Rename `<module>_INTERFACE_LIBRARIES` into `<module>_LIBRARIES` (representing all module-libraries)
+  and introduce `<module>_EXPORTED_LIBRARIES` as a list of all libraries exported by the module.
+
+
+## Build system: Deprecations and removals
+
+- Remove the search of (currently broken) `pkg-config` files for dune packages.
+
+- Remove the `ALLOW_CXXFLAGS_OVERWRITE` configure option. The `CXXFLAGS`
+  overload is still turned on for the JIT compiled Python modules. See the
+  description of the MR
+  https://gitlab.dune-project.org/core/dune-common/-/merge_requests/1251
+  for more details on how to use this feature in the source modules and on
+  some new feature.
+
+- Remove deprecated `add_directory_test_target` function.
+
+- The cmake options `CXX_MAX_STANDARD`, `CXX_MAX_SUPPORTED_STANDARD` and `DISABLE_CXX_VERSION_CHECK`
+  are removed. The cmake function `dune_require_cxx_standard()` is now deprecated.
+
+- Deprecate CMake macro `message_verbose`. Use `message(VERBOSE "message text")` instead.
+  This macro will be removed after Dune 2.10.
+
+- Remove deprecated CMake file `DuneCMakeCompat.cmake` that only contained a
+  deprecation message.
+
+- Remove deprecated CMake function `inkscape_generate_png_from_svg`. Use
+  `dune_create_inkscape_image_converter_target` instead.
+
+- Remove deprecated `rmgenerated.py`. Call `python -m dune remove` with the same
+  arguments instead.
+
+- Remove `DunePythonDeprecations.cmake` that was used to ease the overhaul
+  of Python CMake integration.
+
+- Remove deprecated CMake function `dune_python_install_package`. Use
+  `dune_python_configure_bindings` or `dune_python_configure_package`
+  according to the needed behavior.
+
+
+# Release 2.9
+
+## Dependencies
+In order to build the DUNE core modules you need at least the following software:
+
+- C++ compiler supporting c++-17 language standard, e.g., LLVM Clang >= 5, GCC g++ >= 7
+- CMake >= 3.13
+- Optional: pkg-config to find other optional dependencies
+- Optional: Python >= 3.7 for Python bindings
+
+## Changelog
+
+- Added feature test for lambdas in unevaluated contexts
+  `DUNE_HAVE_CXX_UNEVALUATED_CONTEXT_LAMBDA`. When defined, the C++ language
+  allows to declare lambdas in unevaluated contexts, e.g., `F = decltype([](){})`.
+
+- Multiplication of two matrices using `a*b` is now also implemented if `a` or `b`
+  is a `FieldMatrix` or if both are `DiagonalMatrices`.
+
+- The utility function `transpose(m)` will now return `m.transposed()` if available.
+  Otherwise it returns a wrapper storing a copy (this was a reference before) of `m`.
+  References to matrices can still be captured using `transpose(std::ref(m))` or
+  `transposedView(m)`.
+
+- The transposed of a `FieldMatrix`, `DiagonalMatrix`, and `DynamicMatrix`
+  is now available using the `transposed()` member function.
+
+- Add helper function `resolveRef()` to transparently use `std::reference_wrapper`.
+
+- Add `pragma omp simd` annotations in the LoopSIMD class to improve compiler optimizations
+
+- deprecate Factorial in common/math.hh (use factorial function)
+
+- Add `python -m dune [info|configure|list|remove|dunetype|fix-dunepy]` command to manage
+  just-in-time generated python modules in dune-py
+
+- The storage type `ReservedVector` is extended to follow more closely the `std::vector` and
+  `std::array` interfaces.
+
+## Build System
+
+- Improve the the function `dune_add_library` by separating the target types normal, interface, and
+  object. Additional properties can be passed to the cmake function like `LINK_LIBRARIES`,
+  `OUTPUT_NAME`, and `EXPORT_NAME`
+
+- Remove the variable `DUNE_DEFAULT_LIBS`
+
+- Deprecate cmake file `DuneCMakeCompat.cmake` that just contained the removed function
+  `dune_list_filter`
+
+- Remove deprecated cmake file `DuneMPI.cmake`
+
+- Overhaul of the handling of Dune python packages:
+  python bindings are now enabled by default. Packages are automatically installed
+  either in an internal virtual environment or in an active environment during the
+  module build process.
+  See https://gitlab.dune-project.org/core/dune-common/-/merge_requests/960
+  which also contains a detailed set of instructions on how to update
+  existing python bindings.
+
+- Deprecated `dune_python_install_package`. Use either
+  `dune_python_configure_bindings` (for Python bindings)
+  `dune_python_configure_package` (for pure Python package).
+  See https://gitlab.dune-project.org/core/dune-common/-/merge_requests/1148
+  for more details.
+  Note that this MR also includes
+  https://gitlab.dune-project.org/core/dune-common/-/merge_requests/1103:
+  the Python bindings are not installed editable during the configure stage
+  instead of the build stage.
+
+- dune-py is now build using a simple 'Makefile' per module instead of
+  relying on cmake for each module. The old cmake builder can still be used
+  by exporting the environment variable `DUNE_PY_USE_CMAKEBUILDER=1`.
+
+- Remove deprecated cmake function overload `target_link_libraries`
+
+- Deprecate cmake function `remove_processed_modules`
+
+- The CI system now checks for common spelling mistakes using the `codespell` tool.
+
+## Deprecations and removals
+
+- Helper fallback implementations for `Std::to_false_type`, `Std::to_true_type`,
+  `Std::is_invocable`, and `Std::is_invocable_r` have been removed. Instead,
+  use `Dune::AlwaysFalse`, `Dune::AlwaysTrue`, `std::is_invocable`, and
+  `std::is_invocable_r`.
+
+- The deprecated headers `gcd.hh` and `lcm.hh` are removed. Use `std::gcd`
+  and `std::lcm` instead.
+
+- Both deprecated macros `DUNE_DEPRECATED` and `DUNE_DEPRECATED_MSG(text)`
+  are removed. Use C++14 attribute `[[deprecated]]`. However, be aware
+  that it is no drop-in replacement, as it must be sometimes placed at
+  different position in the code.
+
+- The macros `DUNE_UNUSED` is removed Use C++17's attribute
+  `[[maybe_unused]]` instead, but be aware that it is no drop-in
+  replacement, as it must be sometimes placed at a different position
+  in the code.
+
+- In `callFixedSize`, support handles with `fixedsize()` (lower case s)
+  is removed. Implement `fixedSize()` (camelCase) instead.
+
+- `CollectiveCommunication` and `getCollectiveCommunication` are deprecated
+  and will be removed after Dune 2.9. Use `Communication` respectively
+  `getCommunication` instead.
+
+- The header `power.hh` is deprecated. Use `Dune::power` from
+  `math.hh` instead.
+
+- The deprecated compatibility header `optional.hh` is removed. Include
+  `<optional>` instead.
+
+- The compatibility header `make_array.hh` is deprecated and will be
+  removed after Dune 2.8. Use deduction guide of `std::array` or
+  `std::to_array`.
+
+# Release 2.8
+
+- Set minimal required CMake version in cmake to >= 3.13.
+
+- Python bindings have been moved from dune-python to the core
+  respective core modules.
+
+- Add `instance` method to MPIHelper that does not expect arguments for access
+  to the singleton object after initialization.
+
+- Remove the cmake check for `HAVE_MPROTECT` and also do not define this variable in the
+  `config.h` file. It is defined only inside the header `debugallocator.hh`.
+
+- Remove deprecated type-traits `has_nan`, `is_indexable`, and
+  `is_range`, use the CamelCase versions instead.
+
+- Deprecate fallback implementations `Dune::Std::apply`, `Dune::Std::bool_constant`, and
+  `Dune::Std::make_array` in favor of std c++ implementations.
+
+- Deprecate type traits `Dune::Std::to_false_type`, `Dune::Std::to_true_type`.
+  `Dune::AlwaysFalse` and `Dune::AlwaysTrue` (from header `dune/common/typetraits.hh`)
+  now inherit from `std::true_type` and `std::false_type` and are therefore
+  exact replacements for these two type traits.
+
+- Deprecate fallback implementation `Dune::Std::conjunction`, `Dune::Std::disjunction`,
+  and `Dune::Std::negation`. Use std c++17 implementations.
+
+- Deprecate fallback implementations `Dune::Std::is_callable` and `Dune::Std::is_invocable`.
+  Use C++17 std implementation `std::is_invocable` instead. Be aware that
+  `Dune::Std::is_callable` and `std::is_invocable` are slightly different concepts,
+  since `std::is_invocable` also covers invocation of pointers to member functions
+  and pointers to data members. To additionally constrain for that case,
+  there is now `Dune::IsCallable` (in `dune/common/typetraits.hh`)
+
+- Added `Dune::IsCallable` (in `dune/common/typetraits.hh`) which is
+  an improved version of the deprecated `Dune::Std::is_callable` and allows
+  for checking if a type is a function object type,
+  i.e. has a ()-operator than can be invoked with the given argument types and
+  returns a specified return type.
+
+- Remove c++ feature tests in cmake for existing c++-17 standards. Add default
+  defines for `DUNE_HAVE_CXX_BOOL_CONSTANT`, `DUNE_HAVE_CXX_EXPERIMENTAL_BOOL_CONSTANT`,
+  `DUNE_HAVE_HEADER_EXPERIMENTAL_TYPE_TRAITS`, `DUNE_HAVE_CXX_APPLY`,
+  `DUNE_HAVE_CXX_EXPERIMENTAL_APPLY`, `HAVE_IS_INDEXABLE_SUPPORT` in `config.h` for one
+  more release.
+
+- Add backport of `FindPkgConfig.cmake` from cmake 3.19.4 since there was a bug in
+  an older find module leading to problems finding tbb in debian:10.
+
+- Update the FindTBB cmake module to search for the `TBBConfig.cmake` or the `tbb.pc`
+  file containing the configuration. Add the `AddTBBFlags.cmake` file containing
+  the macro `add_dune_tbb_flags` that must be called to use TBB.
+
+- Set minimal required MPI version to >= 3.0.
+
+- Previous versions of dune-common imported `std::shared_ptr` and `std::make_shared`
+  into the `Dune` namespace.  dune-common-2.8 stops doing that.
+
+- The file `function.hh` is deprecated.  It contained the two base classes
+  `Function` and `VirtualFunction`.  In downstream codes, these should be
+  replaced by C++ function objects, `std::function` etc.
+
+- Python bindings have been moved from the `dune-python` module which is now
+  obsolete. To activate Python bindings the CMake flag
+  `DUNE_ENABLE_PYTHONBINDINGS` needs to be turned on (default is off).
+  Furthermore, flags for either shared library or position independent code
+  needs to be used.
+
+- Support for distributing DUNE modules as python packages has been added.
+  Package meta data is parsed in `packagemetadata.py` from the dune.module file.
+  A script `/bin/dunepackaging.py` was added to generate package files
+  (`setup.py`, `pyproject.toml`) that can also be used to upload packages to
+  the Python Package Index. For a brief description of what is required to add
+  this support to existing dune modules see
+  https://gitlab.dune-project.org/core/dune-common/-/merge_requests/900
+  Note that this can also be used to generate a package for dune modules
+  that don't provide Python bindings.
+
+- Eigenvectors of symmetric 2x2 `FieldMatrix`es are now computed correctly
+  even when they have zero eigenvalues.
+
+- Eigenvectors and values are now also supported for matrices and
+  vectors with field_type being float.
+
+- The `ParameterTreeParser::readINITree` can now directly construct and
+  return a parameter tree by using the new overload without parameter tree
+  argument.
+
+- MPIHelper::instance can now be called without parameters if it was
+  already initialized.
+
+- MPITraits now support complex.
+
+- There is now a matrix wrapper transpose(M) that represents the
+  transpose of a matrix.
+
+## build-system
+
+- The name mangling for Fortran libraries like BLAS and LAPACK is now done
+  without a Fortran compiler. So a Fortran compiler is no longer a built
+  requirement.
+
+- `dune_list_filter` is deprecated and will be removed after Dune 2.8. Use
+  `list(FILTER ...)` introduced by CMake 3.6 instead.
+
+- `ToUniquePtr` is deprecated and will be removed after Dune 2.8. Use
+  `std::unique_ptr` or `std::shared_ptr` instead.
+
+- Remove the CMake options `DUNE_BUILD_BOTH_LIBS` and
+  `DUNE_USE_ONLY_STATIC_LIBS`. Use the default CMake way instead by
+  setting `BUILD_SHARED_LIBS` accordingly. Building both static
+  and shared libraries is no longer supported.
+
+- Deprecate the CMake function `inkscape_generate_png_from_svg`.
+
+- Remove the old and deprecated use of UseLATEX.cmake.
+  `dune_add_latex_document' is a redirection to `add_latex_document`
+  which internally uses `latexmk`.
+
+- Many of the CMake find modules habe been rewritten to use CMake's
+  imported targets. These targets are also used in the DUNE CMake
+  package configuration files, where they might appear in e.g. the
+  dune-module_LIBRARIES. If you do not use the DUNE CMake build system
+  the linker might complain about e.g. METIS::METIS not being
+  found. In that case your either need to use the CMake modules shipped with
+  DUNE or create these targets manually.
+
+## Deprecations and removals
+
+- Remove deprecated header `dune/common/std/memory.hh`; use `<memory>`
+  instead.
+
+- Deprecate header `dune/common/std/utility.hh`; use `<utility>` instead.
+
+- Deprecate header `dune/common/std/variant.hh`; use `<variant>` instead.
+
+- Remove incomplete CPack support that was never used to make an official
+  build or tarball.
+
+- Both macros `DUNE_DEPRECATED` and `DUNE_DEPRECATED_MSG(text)` are
+  deprecated and will be removed after Dune 2.8. Use C++14 attribute
+  `[[deprecated]]` but be aware that it is no drop-in replacement,
+  as it must be sometimes placed at different position in the code.
+
+- The macros `DUNE_UNUSED` is deprecated and will be removed after
+  Dune 2.8. Use C++17's attribute `[[maybe_unused]]` instead, but be
+  aware that it is no drop-in replacement, as it must be sometimes
+  placed at different position in the code.
+  The use of `DUNE_UNUSED_PARAMETER` is discouraged.
+
+- Dune::void_t has been deprecated and will be removed. Please use
+  std::void_t
+
+- Dune::lcd and Dune::gcd are deprecated and will be removed. Please
+  use std::lcd and std::gcd.
+
+- VariableSizeCommunicator::fixedsize has been renamed to FixedSize in
+  line with the communicator changes of dune-grid. The old method will
+  be removed in 2.9.
+
+# Release 2.7
+
+- Added fallback implementation to C++20 feature: `std::identity`.
+
+- A helper class `TransformedRangeView` was added representing a
+  transformed version of a given range using an unary transformation
+  function. The transformation is done on the fly leaving the wrapped
+  range unchanged.
+
+- `dune-common` now provides an implementation of `std::variant` for all compilers
+  that support C++14.  It is contained in the file `dune/common/std/variant.hh`,
+  in the namespace `Dune::Std::`.  If your compiler does support C++17 the
+  implementation in `dune-common` is automatically disabled, and the official
+  implementation from the standard library is used instead.
+
+- By popular demand, dense vectors and matrices like `FieldVector` and `FieldMatrix`
+  now have additional operators.  In particular, there are
+  - Vector = - Vector
+  - Matrix = - Matrix
+  While these two work for any vector or matrix class that inherits from `DenseVector`
+  or `DenseMatrix`, the following additional methods only work for `FieldVector`:
+  - Vector = Scalar * Vector
+  - Vector = Vector * Scalar
+  - Vector = Vector / Scalar
+  Correspondingly, the `FieldMatrix` class now has
+  - Matrix = Matrix + Matrix
+  - Matrix = Matrix - Matrix
+  - Matrix = Scalar * Matrix
+  - Matrix = Matrix * Scalar
+  - Matrix = Matrix / Scalar
+  - Matrix = Matrix * Matrix
+  Note that the operators
+  - Vector = Vector + Vector
+  - Vector = Vector - Vector
+  have been introduced earlier.
+
+- The matrix size functions `N()` and `M()` of `FieldMatrix` and `DiagonalMatrix` can now be used
+  in a `constexpr` context.
+
+- There is now (finally!) a method `power` in the file `math.hh` that computes
+  powers with an integer exponent, and is usable in compile-time expressions.
+  The use of the old power methods in `power.hh` is henceforth discouraged.
+
+-   `FieldMatrix` and `FieldVector` are now [trivially copyable types]
+    if the underlying field type is trivially copyable.
+
+    As a consequence the copy assignment operator of the `DenseVector`
+    class can no longer be used; just avoid going through
+    `DenseVector` and use the real vector type instead
+    (e.g. `FieldVector`).
+
+    [trivially copyable types]: https://en.cppreference.com/w/cpp/named_req/TriviallyCopyable
+
+## Deprecations and removals
+
+- The `VectorSize` helper has been deprecated.  The `size()` method of
+  vectors should be called directly instead.
+
+- Drop support for Python 2. Only Python 3 works with Dune 2.7.
+
+- Support for older version than METIS 5.x and ParMETIS 4.x is deprecated and will be
+  removed after Dune 2.7.
+
+- Deprecated header `dune/common/parallel/collectivecommunication.hh` which will be
+  removed after Dune 2.7. Use dune/common/parallel/communication.hh instead!
+
+- Deprecated header `dune/common/parallel/mpicollectivecommunication.hh` which will be
+  removed after Dune 2.7. Use dune/common/parallel/mpicommunication.hh instead!
+
+## build-system
+
+- When run with an absolute build directory, `dunecontrol` now exposes the root build
+  directory to CMake in the variable `DUNE_BUILD_DIRECTORY_ROOT_PATH`.
+
+  See core/dune-common!542
+
+- The `dune_symlink_to_sources_files` CMake function now has a `DESTINATION` argument.
+
+- Dune no longer applies architecture flags detected by the Vc library
+  automatically.  This applies to all targets that link to Vc explicitly (with
+  `add_dune_vc_flags()`) or implicitly (with `dune_enable_all_packages()`).
+  If you do want to make use of extended architecture features, set the
+  architecture explicitly in the compiler options, e.g. by specifying
+  ```sh
+  CMAKE_FLAGS="-DCMAKE_CXX_FLAGS=-march=native"
+  ```
+  in your opts-file.  Vc also sets compiler options to select a particular C++
+  abi (`-fabi-version` and `-fabi-compat-version`), these continue to be
+  applied automatically.
+
+  See core/dune-common!677
+
+- `FindParMETIS.cmake` assumes METIS was found first using `FindMETIS.cmake` and does not
+  longer try to find METIS itself.
+
+- The `inkscape_generate_png_from_svg` CMake function is deprecated and will be removed
+  after 2.7.
+
+- LaTeX documents can now be built using `latexmk` with the help of UseLatexmk.cmake's
+  `add_latex_document`. `dune_add_latex_document` will use the new way of calling
+  LaTeX when the first argument is `SOURCE`. As a side effect, in-source builds are
+  supported, too. The old function call and UseLATEX.cmake are deprecated and will be
+  removed after 2.7.
+
+  See core/dune-common!594
+
+- The build system has learned some new tricks when creating or looking for the Python virtualenv:
+  When using an absolute build directory with `dunecontrol`, the virtualenv will now be placed
+  directly inside the root of the build directory hierarchy in the directory `dune-python-env`.
+  This should make it much easier to actually find the virtualenv and also avoids some corner
+  cases where the build system would create multiple virtualenvs that did not know about each
+  other. This behavior can be disabled by setting
+  `DUNE_PYTHON_EXTERNAL_VIRTUALENV_FOR_ABSOLUTE_BUILDDIR=0`.
+  If you need even more precise control about the location of the virtualenv, you can now also
+  directly set the CMake variable `DUNE_PYTHON_VIRTUALENV_PATH` to the directory in which to
+  create the virtualenv.
+
+# Release 2.6
+
+**This release is dedicated to Elias Pipping (1986-2017).**
+
+- New class `IntegralRange<integral_type>` and free standing function
+  `range` added, providing a feature similar to Python's `range` function:
+  ```
+    for (const auto &i : range(5,10))
+  ```
+  See core/dune-common!325
+
+- `Dune::array` was deprecated, use `std::array` from <array> instead.
+   Instead of `Dune::make_array`, use `Dune::Std::make_array`
+   from dune/common/std/make_array.hh
+   and instead of `Dune::fill_array` use `Dune::filledArray`
+   from dune/common/filledarray.hh.`
+
+    See core/dune-common!359
+
+- The `DUNE_VERSION...` macros are deprecated use the new macros
+  `DUNE_VERSION_GT`, `DUNE_VERSION_GTE`, `DUNE_VERSION_LTE`, and
+  `DUNE_VERSION_LT` instead.
+
+    See core/dune-common!329
+
+- Added some additional fallback implementation to C++17 features:
+  (e.g. `optional`, `conjunction`, `disjunction`)
+
+- `makeVirtualFunction`:
+  allows to easily convert any function object (e.g. lambda) to a `VirtualFunction`
+
+    See core/dune-common!282
+
+- Added infrastructure for explicit vectorization *(experimental)*
+
+    We added experimental support for SIMD data types. We currently
+    provide infrastructure to use [Vc](https://github.com/VcDevel/Vc)
+    and some helper functions to transparently switch between scalar data
+    types and SIMD data types.
+
+- `FieldMatrix` now has experimental support for SIMD types from
+  [Vc](https://github.com/VcDevel/Vc) as field types.
+
+    See core/dune-common!121
+
+## build-system
+
+- Variables passed via `dunecontrol`'s command `--configure-opts=..` are now
+  added to the CMake flags.
+
+- Bash-style variables which are passed to `dunecontrol`'s command `configure-opts`
+  are no longer transformed to their equivalent CMake command. Pass
+  `-DCMAKE_C_COMPILER=gcc` instead of `CC=gcc`.
+
+- Added support for modules providing additional Python modules or bindings.

CMakeLists.txt

-# set up project
-project("dune-common" C CXX)
+# SPDX-FileCopyrightInfo: Copyright © DUNE Project contributors, see file LICENSE.md in module root
+# SPDX-License-Identifier: LicenseRef-GPL-2.0-only-with-DUNE-exception
 
-# general stuff
-cmake_minimum_required(VERSION 2.8.6)
+cmake_minimum_required(VERSION 3.16)
+project(dune-common LANGUAGES C CXX)
+
+# CMake 3.29.1 is incompatible as it removed PACKAGE_PREFIX_DIR
+if (CMAKE_VERSION VERSION_EQUAL 3.29.1)
+  message(FATAL_ERROR "CMake 3.29.1 is not compatible with Dune. Use a different CMake version.")
+endif()
 
 # make sure our own modules are found
-set(CMAKE_MODULE_PATH ${CMAKE_MODULE_PATH} "${PROJECT_SOURCE_DIR}/cmake/modules")
+list(APPEND CMAKE_MODULE_PATH ${PROJECT_SOURCE_DIR}/cmake/modules)
 
-# set the script dir for the macros.
-set(DUNE_COMMON_SCRIPT_DIR "${PROJECT_SOURCE_DIR}/cmake/scripts")
+set(THREADS_PREFER_PTHREAD_FLAG TRUE CACHE BOOL "Prefer -pthread compiler and linker flag")
 
 #include the dune macros
 include(DuneMacros)
 
+# deactivate global include-directories for dune-common
+dune_policy(SET DP_DEFAULT_INCLUDE_DIRS NEW)
+
+# deactivate global calls to add_dune_all_flags in tests
+dune_policy(SET DP_TEST_ADD_ALL_FLAGS NEW)
+
 # start a dune project with information from dune.module
 dune_project()
 
+# Create a target for dune-common with a Dune::Common alias
+dune_add_library(dunecommon EXPORT_NAME Common NAMESPACE Dune::)
+
+# set include directories for dunecommon library
+dune_default_include_directories(dunecommon PUBLIC)
+
+# minimal c++ standard required
+target_compile_features(dunecommon PUBLIC cxx_std_20)
+
+# Set properties to the dunecommon target
+add_dune_blas_lapack_flags(dunecommon)
+add_dune_tbb_flags(dunecommon)
+
+# collect dependencies to be added into the dune-common-config.cmake files
+set(DUNE_COMMON_PACKAGE_DEPENDENCIES
+  [[set(THREADS_PREFER_PTHREAD_FLAG TRUE CACHE BOOL "Prefer -pthread compiler and linker flag")]])
+
+# since dunecommon is exported its linked libs must be provided downstream too
+if (LAPACK_FOUND)
+  list(APPEND DUNE_COMMON_PACKAGE_DEPENDENCIES "find_dependency(LAPACK)")
+elseif (BLAS_FOUND)
+  list(APPEND DUNE_COMMON_PACKAGE_DEPENDENCIES "find_dependency(BLAS)")
+endif()
+if (Threads_FOUND)
+  list(APPEND DUNE_COMMON_PACKAGE_DEPENDENCIES "find_dependency(Threads)")
+endif()
+if (TBB_FOUND)
+  list(APPEND DUNE_COMMON_PACKAGE_DEPENDENCIES "find_dependency(TBB)")
+endif()
+
 # add subdirectories to execute CMakeLists.txt there
-add_subdirectory("lib")
-add_subdirectory("share")
-add_subdirectory("dune")
-add_subdirectory("bin")
-add_subdirectory("m4")
-add_subdirectory("am")
-add_subdirectory("doc")
-add_subdirectory("cmake/modules")
-add_subdirectory("cmake/scripts")
-
-# finalize the dune project, e.g. generating config.h etc.
+add_subdirectory(bin)
+add_subdirectory(cmake)
+add_subdirectory(doc)
+add_subdirectory(dune)
+add_subdirectory(lib)
+add_subdirectory(share)
+
+# if Python bindings are enabled, include necessary sub directories.
+if(DUNE_ENABLE_PYTHONBINDINGS)
+  add_subdirectory(python)
+endif()
+
+# write contents into DUNE_CUSTOM_PKG_CONFIG_SECTION, which will be injected into dune-common-config.cmake
+string(JOIN "\n" DUNE_CUSTOM_PKG_CONFIG_SECTION
+  # make sure that Find<module>.cmake provided by dune-common can be found by cmake
+  [[list(APPEND CMAKE_MODULE_PATH "${dune-common_MODULE_PATH}")]]
+  ${DUNE_COMMON_PACKAGE_DEPENDENCIES}
+)
+
+# finalize the dune project, e.g. generating config.h, dune-common-config.cmake, etc.
 finalize_dune_project()

CONTRIBUTING.md

+<!--
+SPDX-FileCopyrightInfo: Copyright © DUNE Project contributors, see file LICENSE.md in module root
+SPDX-License-Identifier: LicenseRef-GPL-2.0-only-with-DUNE-exception
+-->
+
+Contributing to the Dune Core Modules
+=====================================
+
+You've squashed an annoying bug or implemented a nifty new feature in DUNE?
+And you're willing to share your improvements with the community? This page
+explains how to get those changes to us and what to take care of.
+
+Take a look at the DUNE coding style
+------------------------------------
+
+Your work will enjoy much smoother sailing if you take a look at the [Coding
+Style](https://dune-project.org/dev/codingstyle/) and try to stick to it with
+your changes. We understand that everyone has their personal preferences and
+that there is no such thing as the *right* coding style (in the end, it's a
+matter of taste), but DUNE is a pretty large project, and a consistent way of
+doing things really helps a lot when trying to find your way around a body of
+code as big as DUNE.
+
+Make sure to install the Whitespace Hook before starting to work, because
+our repositories enforce certain rules about whitespace and will not accept
+commits that violate those rules. And a developer will be much more motivated
+to merge your patch if doing so does not involve fixing a bunch of tab-based
+indentations that you inadvertently added as part of your changes
+
+Tests / Automated Testing
+-------------------------
+
+When contributing a new feature to Dune it should be accompanied by a unit test.
+There are currently untested features and adding unit tests for such features
+is always a good contribution.
+When modifying a currently untested feature, add a unit test.
+
+Unit tests in the Dune core modules are added in the `test` directory
+of the folder containing the header with the feature code.
+
+In Dune modules, tests are added to the
+test suite (which is tested automatically with Gitlab-CI, e.g., when opening a merge request)
+by adding them with the [`dune_add_test` function](https://gitlab.dune-project.org/core/dune-common/-/blob/master/cmake/modules/DuneTestMacros.cmake)
+in the `CMakeLists.txt` file of the test folder.
+Using `dune_add_test` ensures that the test is added to the top level `build_tests` target
+which is used in the CI framework to build all tests (and can of course
+also be used locally to build all tests of a Dune module, `make build_tests`).
+The function also provides several convenient features such as the possibility
+to automatically run a test several times with different numbers of processors.
+
+If a specific more complex test setup is not supported by `dune_add_test`,
+the test has to be added explicitly to the `build_tests` target. However,
+for such cases we recommend instead to try to improve the `dune_add_test`
+function to support the use case.
+
+
+Use Git to your advantage
+-------------------------
+
+We know, Git can be a bit daunting at first, but trust us, it's really worth
+investing half an hour to learn the basics! Even though you don't have any
+commit rights to the DUNE repositories, Git still allows you to create local
+commits on your machine, avoiding the usual ugly business of creating backup
+copies, copying around code in files, commenting and uncommenting variants etc.
+And when you're done and send the changes to us, we can simply import those
+commits into our repositories. That saves a lot of time and when your changes
+can be applied in five minutes using two or three commands, chances are a
+developer will much more easily find the time to do so. Git is really popular,
+so there are tons of tutorials all over the web. Here are some pointers:
+
+* http://try.github.io/ is a very quick, hands-down introduction
+  to Git that allows you to try out Git directly in your browser.
+  Requires a GitHub account to continue at some point, though.
+* http://git-scm.com/book is a very well-written and detailed resource
+  for all things Git. Chapter 2 is a great introduction to Git that also explains
+  a little bit how Git works, which really helps to reduce the number of
+  *WTF just happened?* moments. ;-)
+* http://eagain.net/articles/git-for-computer-scientists/ is a short and
+  sweet explanation of what Git does at a fundamental level - just the thing for
+  scientists! ;-)
+* http://git-scm.com/doc/ext is a collection of both introductory and
+  more in-depth Git resources.
+
+Whatever you do, make sure to set your Git identity so that the commits tell us who authored them!
+
+Getting the changes to us
+-------------------------
+
+You should get your changes to us in the following way:
+* Get an account for [our GitLab instance](http://gitlab.dune-project.org).
+* Fork the core module that you want to contribute to, just
+  as you would do on GitHub.
+* Push your changes to your fork on some branch.
+* Open a merge request using the branch you pushed your changes
+  to as the source branch and the master of the core module repository
+  as the target branch. GitLab will usually ask you about opening
+  a merge request if you browse it right after pushing to some branch.
+* Follow the discussion on the merge request to see what improvements
+  should be done to the branch before merging.
+
+If you have any questions or complaints about this workflow of
+contributing to Dune, please rant on the
+[dune-devel mailing list](mailto:dune-devel@lists.dune-project.org).

COPYING

-Copyright holders:
-
-2003--2010    Peter Bastian
-2004--2013    Markus Blatt
-2013          Andreas Buhr
-2011--2013    Ansgar Burchardt
-2004--2005    Adrian Burri
-2014          Benjamin Bykowski (may appear in the logs as "Convex Function")
-2006--2013    Andreas Dedner
-2003          Marc Droske
-2003--2013    Christian Engwer
-2004--2012    Jorrit Fahlke
-2008--2013    Bernd Flemisch
-2013          Christoph Gersbacher
-2005--2013    Carsten Gräser
-2010--2013    Christoph Grüninger
-2006          Bernhard Haasdonk
-2012--2013    Olaf Ippisch
-2013          Dominic Kempf
-2009          Leonard Kern
-2013          Torbjörn Klatt
-2003--2013    Robert Klöfkorn
-2005--2007    Sreejith Pulloor Kuttanikkad
-2012--2013    Arne Morten Kvarving
-2010--2013    Andreas Lauser
-2007--2011    Sven Marnach
-2012--2013    Tobias Malkmus
-2010          Rene Milk
-2011--2013    Steffen Müthing
-2003--2006    Thimo Neubauer
-2011          Rebecca Neumann
-2008--2013    Martin Nolte
-2004--2005    Mario Ohlberger
-2008--2013    Elias Pipping
-2011          Dan Popovic
-2009          Atgeirr Rasmussen
-2003--2013    Oliver Sander
-2006--2011    Uli Sack
-2006          Klaus Schneider
-2004          Roland Schulz
-2009--2012    Bård Skaflestad
-2012          Matthias Wohlmuth
-2011          Jonathan Youett
-
-
-The DUNE library and headers are licensed under version 2 of the GNU
-General Public License (see below), with a special exception for
-linking and compiling against DUNE, the so-called "runtime exception."
-The license is intended to be similar to the GNU Lesser General
-Public License, which by itself isn't suitable for a template library.
-
-The exact wording of the exception reads as follows:
-
-   As a special exception, you may use the DUNE source files as part
-   of a software library or application without restriction.
-   Specifically, if other files instantiate templates or use macros or
-   inline functions from one or more of the DUNE source files, or you
-   compile one or more of the DUNE source files and link them with
-   other files to produce an executable, this does not by itself cause
-   the resulting executable to be covered by the GNU General Public
-   License.  This exception does not however invalidate any other
-   reasons why the executable file might be covered by the GNU General
-   Public License.
-
-
-		    GNU GENERAL PUBLIC LICENSE
-		       Version 2, June 1991
-
- Copyright (C) 1989, 1991 Free Software Foundation, Inc.
- 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-			    Preamble
-
-  The licenses for most software are designed to take away your
-freedom to share and change it.  By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users.  This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it.  (Some other Free Software Foundation software is covered by
-the GNU Library General Public License instead.)  You can apply it to
-your programs, too.
-
-  When we speak of free software, we are referring to freedom, not
-price.  Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
-
-  To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
-  For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have.  You must make sure that they, too, receive or can get the
-source code.  And you must show them these terms so they know their
-rights.
-
-  We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
-  Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software.  If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-
-  Finally, any free program is threatened constantly by software
-patents.  We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary.  To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
-
-  The precise terms and conditions for copying, distribution and
-modification follow.
-
-		    GNU GENERAL PUBLIC LICENSE
-   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
-  0. This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License.  The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language.  (Hereinafter, translation is included without limitation in
-the term "modification".)  Each licensee is addressed as "you".
-
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope.  The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
-
-  1. You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
-
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
-
-  2. You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
-    a) You must cause the modified files to carry prominent notices
-    stating that you changed the files and the date of any change.
-
-    b) You must cause any work that you distribute or publish, that in
-    whole or in part contains or is derived from the Program or any
-    part thereof, to be licensed as a whole at no charge to all third
-    parties under the terms of this License.
-
-    c) If the modified program normally reads commands interactively
-    when run, you must cause it, when started running for such
-    interactive use in the most ordinary way, to print or display an
-    announcement including an appropriate copyright notice and a
-    notice that there is no warranty (or else, saying that you provide
-    a warranty) and that users may redistribute the program under
-    these conditions, and telling the user how to view a copy of this
-    License.  (Exception: if the Program itself is interactive but
-    does not normally print such an announcement, your work based on
-    the Program is not required to print an announcement.)
-
-These requirements apply to the modified work as a whole.  If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works.  But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
-  3. You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
-
-    a) Accompany it with the complete corresponding machine-readable
-    source code, which must be distributed under the terms of Sections
-    1 and 2 above on a medium customarily used for software interchange; or,
-
-    b) Accompany it with a written offer, valid for at least three
-    years, to give any third party, for a charge no more than your
-    cost of physically performing source distribution, a complete
-    machine-readable copy of the corresponding source code, to be
-    distributed under the terms of Sections 1 and 2 above on a medium
-    customarily used for software interchange; or,
-
-    c) Accompany it with the information you received as to the offer
-    to distribute corresponding source code.  (This alternative is
-    allowed only for noncommercial distribution and only if you
-    received the program in object code or executable form with such
-    an offer, in accord with Subsection b above.)
-
-The source code for a work means the preferred form of the work for
-making modifications to it.  For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable.  However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
-  4. You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License.  Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
-  5. You are not required to accept this License, since you have not
-signed it.  However, nothing else grants you permission to modify or
-distribute the Program or its derivative works.  These actions are
-prohibited by law if you do not accept this License.  Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
-
-  6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions.  You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
-this License.
-
-  7. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License.  If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all.  For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices.  Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
-  8. If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded.  In such case, this License incorporates
-the limitation as if written in the body of this License.
-
-  9. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time.  Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number.  If the Program
-specifies a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation.  If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
-Foundation.
-
-  10. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission.  For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this.  Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
-			    NO WARRANTY
-
-  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
-
-  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
-		     END OF TERMS AND CONDITIONS
-
-	    How to Apply These Terms to Your New Programs
-
-  If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
-  To do so, attach the following notices to the program.  It is safest
-to attach them to the start of each source file to most effectively
-convey the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
-    <one line to give the program's name and a brief idea of what it does.>
-    Copyright (C) <year>  <name of author>
-
-    This program is free software; you can redistribute it and/or modify
-    it under the terms of the GNU General Public License as published by
-    the Free Software Foundation; either version 2 of the License, or
-    (at your option) any later version.
-
-    This program is distributed in the hope that it will be useful,
-    but WITHOUT ANY WARRANTY; without even the implied warranty of
-    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-    GNU General Public License for more details.
-
-    You should have received a copy of the GNU General Public License
-    along with this program; if not, write to the Free Software
-    Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA
-
-
-Also add information on how to contact you by electronic and paper mail.
-
-If the program is interactive, make it output a short notice like this
-when it starts in an interactive mode:
-
-    Gnomovision version 69, Copyright (C) year name of author
-    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
-    This is free software, and you are welcome to redistribute it
-    under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate
-parts of the General Public License.  Of course, the commands you use may
-be called something other than `show w' and `show c'; they could even be
-mouse-clicks or menu items--whatever suits your program.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary.  Here is a sample; alter the names:
-
-  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
-  `Gnomovision' (which makes passes at compilers) written by James Hacker.
-
-  <signature of Ty Coon>, 1 April 1989
-  Ty Coon, President of Vice
-
-This General Public License does not permit incorporating your program into
-proprietary programs.  If your program is a subroutine library, you may
-consider it more useful to permit linking proprietary applications with the
-library.  If this is what you want to do, use the GNU Lesser General
-Public License instead of this License.

COPYING

+LICENSE.md
\ No newline at end of file

INSTALL

+<!--
+SPDX-FileCopyrightInfo: Copyright © DUNE Project contributors, see file LICENSE.md in module root
+SPDX-License-Identifier: LicenseRef-GPL-2.0-only-with-DUNE-exception
+-->
+
 Installation Instructions
 =========================
 
@@ -14,8 +19,8 @@ list of available modules.
 
 To compile the modules Dune has to check several components of
 your system and whether prerequisites within the modules are met. For
-the ease of users we have designed a custom build system on top of the
-automake tools. Run
+the ease of users we have designed a custom build system on top of CMake.
+Run
 
   ./dune-common/bin/dunecontrol all
 
@@ -37,7 +42,7 @@ need to run
 to install Dune (you may need root-permissions for the install
 part depending on the prefix set)
 
-A more comprehensive introduction to the build system can be found in [2].
+A more comprehensive introduction to the build system can be found in [0].
 
 Passing options to the build process
 ------------------------------------
@@ -45,50 +50,31 @@ Passing options to the build process
 Using the dunecontrol script the following atomic commands can be
 executed:
 
-- autogen (runs autogen in each module, only needed when downloaded
-  via svn)
-- configure (runs the configure tests for each module
-- exec (executes a command in each module directory)
-- make (runs make for each module)
-- update (updates the svn version)
+- configure (runs the CMake configuration tests for each module)
+- exec (executes a command in each module source directory)
+- bexec (executes a command in each module build directory)
+- make (builds each module)
+- update (updates the Git or Subversion version)
 
-The composite command all simply runs autogen, configure and make for
+The composite command all simply runs configure and make for
 each module.
 
-As it is often not convenient (and for the target all impossible) to
-specify the options for each command as parameters after the call, one
-can pass the options via file specified by the --opts=<file>
-option. For each atomic command one specify the options via a ine
-
-<COMMANY_UPPERCASE>_FLAGS=<flags> # e.g.: MAKE_FLAGS=install
-
-The available options for make and svn are the natural ones. The
-configure commands available can be found by issuing
-
-dunecontrol --only=dune-common configure --help
-
-and for autogen by
-
-dunecontrol --only=dune-common autogen --help
-
-(In the svn version this has to be calles after running autogen.)
+As it is often not convenient to specify the desired options after
+the duncontroll call, one can pass the options via a file specified
+by the --opts=<file> option. Specify the options via the variable
 
+  CMAKE_FLAGS=<flags>
 
 An example of an options file is
 
-  # use a special compiler (g++ version 3.4) and install to a custom
-  # directory, default is /usr/local/bin
-  CONFIGURE_FLAGS="CXX=g++-3.4 --prefix='/tmp/Hu Hu'"
-  # Set the default target of make to install. Now the call above will
-  # not just build the DUNE modules but also install it
-   MAKE_FLAGS=install
-  # The default versions of automake and autogen are not sufficient
-  # therefore we need to specify what versions to use
-  AUTOGEN_FLAGS="--ac=2.59 --am=1.9
+  # use a special compiler (g++ version 14.0),
+  # install to a custom directory, default is /usr/local/bin,
+  # disable the external library SuperLU,
+  # and use Ninja-build instead of make as the build-tool
+  CMAKE_FLAGS="-DCMAKE_CXX_COMPILER=g++-14 -DCMAKE_INSTALL_PREFIX='/tmp/HuHu' -DCMAKE_DISABLE_FIND_PACKAGE_SuperLU=true -GNinja"
 
 Links
 -----
 
-0. http://www.dune-project.org/doc/installation-notes.html
-1. http://www.dune-project.org/download.html
-2. http://dune-project.org/doc/buildsystem/buildsystem.pdf
+0. https://www.dune-project.org/doc/installation
+1. https://dune-project.org/releases/

LICENSE.md

+Copyright holders:
+==================
+
+2015--2017    Marco Agnese
+2015          Martin Alkämper
+2003--2019    Peter Bastian
+2004--2024    Markus Blatt
+2013          Andreas Buhr
+2020--2023    Samuel Burbulla
+2011--2023    Ansgar Burchardt
+2004--2005    Adrian Burri
+2014          Benjamin Bykowski (may appear in the logs as "Convex Function")
+2014          Marco Cecchetti
+2018          Matthew Collins
+2006--2024    Andreas Dedner
+2018--2021    Nils-Arne Dreier
+2003          Marc Droske
+2003--2024    Christian Engwer
+2004--2020    Jorrit Fahlke
+2016          Thomas Fetzer
+2008--2017    Bernd Flemisch
+2013--2014    Christoph Gersbacher
+2017--2020    Janick Gerstenberger
+2015          Stefan Girke
+2015--2017    Felix Gruber
+2005--2024    Carsten Gräser
+2010--2024    Christoph Grüninger
+2006          Bernard Haasdonk
+2015--2020    René Heß
+2015--2018    Claus-Justus Heine
+2017--2019    Stephan Hilb
+2017--2021    Lasse Hinrichsen
+2012--2013    Olaf Ippisch
+2020--2022    Patrick Jaap
+2020          Liam Keegan
+2013--2022    Dominic Kempf
+2009          Leonard Kern
+2017--2018    Daniel Kienle
+2013          Torbjörn Klatt
+2003--2024    Robert Klöfkorn
+2017--2024    Timo Koch
+2005--2007    Sreejith Pulloor Kuttanikkad
+2012--2016    Arne Morten Kvarving
+2010--2014    Andreas Lauser
+2016--2021    Tobias Leibner
+2015          Lars Lubkoll
+2012--2017    Tobias Malkmus
+2007--2011    Sven Marnach
+2010--2017    René Milk
+2022--2024    Alexander Müller
+2019--2020    Felix Müller
+2011--2019    Steffen Müthing
+2018--2024    Lisa Julia Nebel
+2003--2006    Thimo Neubauer
+2011          Rebecca Neumann
+2008--2018    Martin Nolte
+2014          Andreas Nüßing
+2004--2005    Mario Ohlberger
+2014          Steffen Persvold
+2008--2017    Elias Pipping
+2021          Joscha Podlesny
+2011          Dan Popovic
+2017--2024    Simon Praetorius
+2009          Atgeirr Rasmussen
+2017--2020    Lukas Renelt
+2019--2024    Santiago Ospina De Los Ríos
+2006--2014    Uli Sack
+2003--2024    Oliver Sander
+2006          Klaus Schneider
+2004          Roland Schulz
+2015          Nicolas Schwenck
+2016          Linus Seelinger
+2009--2014    Bård Skaflestad
+2019          Henrik Stolzmann
+2024          Andreas Thune
+2012          Matthias Wohlmuth
+2011--2016    Jonathan Youett
+
+This Licence does not cover the header files taken from the
+[pybind11 project][pybind11] which are included here
+(`dune/python/pybind11`) together with their own [licence file][pybind11Licence].
+
+The DUNE library and headers are licensed under version 2 of the GNU
+General Public License (see below), with a special exception for
+linking and compiling against DUNE, the so-called "runtime exception."
+The license is intended to be similar to the GNU Lesser General
+Public License, which by itself isn't suitable for a template library.
+
+The exact wording of the exception reads as follows:
+
+   As a special exception, you may use the DUNE source files as part
+   of a software library or application without restriction.
+   Specifically, if other files instantiate templates or use macros or
+   inline functions from one or more of the DUNE source files, or you
+   compile one or more of the DUNE source files and link them with
+   other files to produce an executable, this does not by itself cause
+   the resulting executable to be covered by the GNU General Public
+   License.  This exception does not however invalidate any other
+   reasons why the executable file might be covered by the GNU General
+   Public License.
+
+
+        GNU GENERAL PUBLIC LICENSE
+           Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+ 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+          Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+        GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+          NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+         END OF TERMS AND CONDITIONS
+
+      How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program; if not, write to the Free Software
+    Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.
+
+[pybind11]: https://github.com/pybind/pybind11
+[pybind11Licence]: https://github.com/pybind/pybind11/blob/master/LICENSE

LICENSES/BSD-3-Clause.txt

+Copyright (c) <year> <owner>. 
+
+Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
+
+3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

LICENSES/FSFAP.txt

+Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved.  This file is offered as-is, without any warranty.

LICENSES/LicenseRef-GPL-2.0-only-with-DUNE-exception.txt

+The DUNE library and headers are licensed under version 2 of the GNU
+General Public License (see below), with a special exception for
+linking and compiling against DUNE, the so-called "runtime exception."
+The license is intended to be similar to the GNU Lesser General
+Public License, which by itself isn't suitable for a template library.
+
+The exact wording of the exception reads as follows:
+
+   As a special exception, you may use the DUNE source files as part
+   of a software library or application without restriction.
+   Specifically, if other files instantiate templates or use macros or
+   inline functions from one or more of the DUNE source files, or you
+   compile one or more of the DUNE source files and link them with
+   other files to produce an executable, this does not by itself cause
+   the resulting executable to be covered by the GNU General Public
+   License.  This exception does not however invalidate any other
+   reasons why the executable file might be covered by the GNU General
+   Public License.
+
+
+        GNU GENERAL PUBLIC LICENSE
+           Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+ 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+          Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+        GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+          NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+         END OF TERMS AND CONDITIONS
+
+      How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program; if not, write to the Free Software
+    Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.

Makefile.am

-# $Id$
-
-# we need the module file to be able to build via dunecontrol
-EXTRA_DIST= CMakeLists.txt dune.module
-
-# don't follow the full GNU-standard
-# we need automake 1.9 or newer
-AUTOMAKE_OPTIONS = foreign 1.9
-
-SUBDIRS = cmake dune lib share doc bin m4 am
-
-# use configured compiler for "make distcheck"
-DISTCHECK_CONFIGURE_FLAGS = CXX="$(CXX)" CC="$(CC)" --enable-parallel=@ENABLE_PARALLEL@ MPICC="$(MPICC)"
-
-include $(top_srcdir)/am/global-rules
-include $(top_srcdir)/am/top-rules
-
-# Distribute and install config.h.cmake
-configdir = $(datadir)/dune-common
-dist_config_DATA = config.h.cmake
-
-include $(top_srcdir)/am/cmake-pkg-config

README.SVN

-Preparing the SVN-sources
-=========================
-
-Additional to the software mentioned in README you'll need the
-following programs installed on your system:
-
-  automake >= 1.9
-
-  autoconf >= 2.62
-
-  libtool
-
-For the documentation to build you'll need doxygen, wml, convert and latex
-installed.
-
-Dune also features a self-test. As some components (e.g. Albert,
-UG) depend on external libraries their self-tests will only run if
-those libraries are found. The paths to their installation prefix
-would then need to be passed via --with-...= parameters to configure.
-
-Important!  If you don't want to develop Dune itself you won't need to
-provide external components! The Dune-library and -headers are
-independent of other libraries, instead the applications can choose
-which parts to use.
-