[Dune] State of source in executable

[Dominic Kempf]

Hey Max,

not sure whether this is what you are looking for, but I know that people
use "supermodules" for that purpose. A super module is a repository, which
has all the needed dune modules as submodules through the git-submodule
mechanism. That way you can pin all the modules to specific revisions
through commits in the supermodule. It doesnt handle uncommitted changes of
course, but I would not recommend such a mechanism include those anyway.
The approach is somewhat fiddly, but does not need support from the dune
side at all.

Best,
Dominic

On Tue, Jun 27, 2017 at 3:01 PM, Christian Engwer <
christian.engwer at uni-muenster.de> wrote:

> Hi Max,
>
> > I was wondering whether there was a dune-internal solution to have an
> > executable report the state of its sources. I was thinking of some script
> > that is called at compile-time through a macro (if possible) and exploits
> > git functionality in the sense that it provides the SHA1-IDs of all
> > dune-modules used as well as uncommited changes.
>
> we once had such functionality (in the time of subversion), but
> oviously this does not work anymore. I also would like to have
> something similar, in order to ease reproducibility of numerical
> experiments.
>
> I would even suggest to include such functionality in dune-common
> (once we have figured out how to do it properly...).
>
> First question would be, it is OK to limit ourselfs to git and
> installed modules?
>
> Ciao
> Christian
>
> _______________________________________________
> Dune mailing list
> Dune at lists.dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dune-project.org/pipermail/dune/attachments/20170627/32415af3/attachment.htm>