[Dune-devel] Mixing master and releases

[Andreas Dedner]

Hi.
I think there is a good argument to force version matching - it makes
helping people fix problems much easier. Even now its difficult enough to
get people to hand in good bug reports (which gcc version, which automake,
what does the opts file look like....).
At the moment its nice to at least just have one version of the core
modules to deal
with, instead of having to figure out which version of each module is
being used.
Also its makes it more difficult for somebody else to verify the problem
because
you would basically need to install the other guys module versions.
Furthermore
matching versions is all we can test for during nightly builds.
Best
Andreas

On 24.02.2014 08:57, Markus Blatt wrote:
> On Mon, Feb 24, 2014 at 09:45:13AM +0100, Oliver Sander wrote:
>>> Sure it works, but the question is how long does it work. We did it
>>> because we always did it this way 
>> sorry, but "because we always did it this way" is not a good reason for me.
> That was never meant as an argument.
>
>> My proposal: revert all dependencies to 2.3 and keep them there until the first
>> problems show up.  I am even tempted to propose that we may consider hacking
>> around the first few version incompatibilities with the preprocessor (that's what
>> version.hh is for, after all).
> Actually, I do not have any strong feelings about version
> dependencies, despite that they are nearly always broken (just take
> dune-grid 1.0 and which demands for dune-common >=1.0 LOL) and a lot
> of work.
>
> To me the CMake version systems makes some sense. There, the packages
> export which to which of their own versions they are compatible. Kind
> of contradicts the pkg-config stuff, though.
>
> Markus
>
>
> _______________________________________________
> Dune-devel mailing list
> Dune-devel at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dune-project.org/pipermail/dune-devel/attachments/20140224/ce3b58de/attachment.htm>