[Dune] [#987] build system: do not force all modules to place their headers in $DUNE_MODULE_ROOT/dune/

[Dune]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#987 - build system: do not force all modules to place their headers in $DUNE_MODULE_ROOT/dune/
User who did this - Jö Fahlke (joe)

----------
This has bugged me as well in the past.

I see no technical reason for enforcing the dune/ path prefix.  This may be a reasonable style requirement for core modules and modules closely related to the core.  But other modules should not be forced into a particular scheme.  In the case of dumux this would be particularly awkward, since a far as I understand, the "du" in dumux already stands for dune.  Another awkward example is neurodune with dune/neurodune/.

This becomes particularly awkward if a project builds on top of another library as well as dune.  The other library may bring it's own requirement on the path (after all, if we impose some random requirement, why shouldn't they do the same?)

Are there maybe any non-technical reasons for this requirement?

Note: The whole issue applies only to library modules, i.e. modules that are intended to be used by other modules.  Pure application modules are not affected.

----------

More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=987#comment2937

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.