<div dir="ltr"><div dir="ltr">Matthias, WADR, your statement seems, at least on the surface, to indicate an incredibly fragile process. How can you possibly maintain stability and reproducibility if the dependencies can be changed at will?<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jul 31, 2020 at 2:27 AM Matthias Kuhn <<a href="mailto:matthias@opengis.ch">matthias@opengis.ch</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div>One thing to keep in mind is that even
the main qgis installers/distributions do not have fixed
dependency versions. Using downloaded macOS QGIS will have
different dependencies than Windows and so will all the linux/*nix
flavors.</div>
<div><br>
</div>
<div>On 7/31/20 7:14 AM, Ari Meyer wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>@Nyall, that proposal appears to be specific to plugins --
not sure if that's the best place to discuss this issue.<br>
</div>
<div>@Greg: I found that many of the exact dependencies were not
even available through the main channels. So if the QGIS devs
compile/build against such versions, I'm not sure there's an
easy way to even specify such a conda recipe, unless all those
dependencies are also made available somehow. I didn't expect
that those versions would not even be there with the others
for the various libraries. Could this imply that the library
developers don't want those versions to be used? Not sure.<br>
</div>
<div><br>
</div>
<div>As a user and developer, I just want to be sure that if I
pull down conda-forge qgis version X that I will get the same
effective distribution as contained in downloadable installer
version X. Right now, we are getting a very different set of
dependencies.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Ari</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Jul 30, 2020 at 6:44
PM Greg Troxel <<a href="mailto:gdt@lexort.com" target="_blank">gdt@lexort.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Nyall
Dawson <<a href="mailto:nyall.dawson@gmail.com" target="_blank">nyall.dawson@gmail.com</a>>
writes:<br>
<br>
> There's a related proposal at<br>
> <a href="https://github.com/qgis/QGIS-Enhancement-Proposals/issues/179" rel="noreferrer" target="_blank">https://github.com/qgis/QGIS-Enhancement-Proposals/issues/179</a>
--<br>
> probably best to keep the discussion on that page.<br>
<br>
Not really about the details of using conda but about the
concept:<br>
<br>
conda's documentation says it runs on "Windows, macOS and
Linux" but<br>
qgis also runs on at least NetBSD and almost certainly other
BSDs.<br>
<br>
it seems that to build something, including qgis the
requirement is<br>
that the things it depends on are present in some way that
is found by<br>
the build. People can choose to do that however they want,
and it<br>
seems funny to me to impose a requirement. If this is
really "let's<br>
publish a conda config file so that people who want to do
that can do<br>
less work", that's of course fine, but if it's more "if you
don't have<br>
conda then you can't build qgis", that's something else.<br>
</blockquote>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
QGIS-Developer mailing list
<a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></pre>
</blockquote>
</div>
</blockquote></div></div>