<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Jürgen<br>
</p>
<br>
<div class="moz-cite-prefix">On 06/11/2018 10:27 PM, Jürgen E.
Fischer wrote:<br>
</div>
<br>
<blockquote type="cite"
cite="mid:20180611202707.gkjfsy7zq6qufkkj@norbit.de">
<blockquote type="cite">
<pre wrap="">The infrastructure in the background is to my knowledge not documented and we
are happy if it just works. And if it breaks if there is someone with
knowledge and access rights to fix things.
</pre>
</blockquote>
<pre wrap="">
The OSGeo4W infrastructure is download.osgeo.org. It's documented in the trac
wiki. The only required access right is a osgeo id with shell access.
There's no building infrastructure. So maintainers have to build their
packages on their own machine and upload them. Some of the package (most of
mine for instance) also contain (-src) packages with the build recipes for the
package.</pre>
</blockquote>
That's good to know, that will make it easier to go on if (and we
don't hope that of course) someone disappears.<br>
<br>
<blockquote type="cite"
cite="mid:20180611202707.gkjfsy7zq6qufkkj@norbit.de">
<pre wrap="">But there currently is no "standardized" way to invoke them, upload the package
and run the packaging scripts. The build recipes are diverse and use cmake,
nmake, ninja, gnu make, batch files, shell scripts (cygwin/mingw) and use
several different version of compilers (multiple versions of MSVC & mingw gcc).
Some even require third party SDKs that cannot be redistributed. There's no
base build system or way to install build dependencies.
AFAIK automated packages only exists for QGIS, GDAL and GRASS - those run on
internal infrastructure (here inhouse for QGIS/GDAL and I think at the
university Martin works for GRASS) and upload the results.
</pre>
<blockquote type="cite">
<pre wrap="">I just stumbled upon a repository from Oslandia [2] that streamlines the
packaging and integrates it with continuous deployment apparently.
</pre>
</blockquote>
<pre wrap="">
Odd that you had to stumbled upon it - this was also presented and discussed at
the Madeira hackfest and it's one of the benifits of moving from github to
gitlab.</pre>
</blockquote>
<br>
Then this must be caused by my absence in Madeira ;)<br>
If required a gitlab mirror of the current github repo to trigger
gitlab-ci builds should be the smallest part to setup within this
infrastructure ;)<br>
<br>
<blockquote type="cite"
cite="mid:20180611202707.gkjfsy7zq6qufkkj@norbit.de">
<pre wrap="">But it currently also depends on internal build servers (at oslandia). It
doesn't upload to the osgeo4w repository, but integrates the repository and has
utility scripts to invoke the build, harvest the packages and add them to taht
repository. So the current packaging scripts would have to be adapted.</pre>
</blockquote>
Reading this and the above paragraph, I think it's a quite good
approach here, proxying to the existing pre-built packages and
building a scripted repo on top that eventually can obsolete
packages one-by-one.<br>
<br>
<blockquote type="cite"
cite="mid:20180611202707.gkjfsy7zq6qufkkj@norbit.de">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">Having such a repository under QGIS or OSGeo umbrella could help to take away
the burden of maintaining the Windows distribution from very few people,
having a pull request review scheme as we have for source code and distribute
the responsibility.
</pre>
</blockquote>
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">In short, having a repository where package scripts and build scripts are
publicly available, forkable, builds are reproducible and where it's possible
to make pull requests.
</pre>
</blockquote>
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">The main question in the first line is probably, is that something which is
considered a QGIS task, an OSGeo task or a task that individual companies
should be taking?
</pre>
</blockquote>
<pre wrap="">
This might introduce a long enough pole to make it bearable for more devs to
touch windows and get more contributors for OSGeo4W. ;)</pre>
</blockquote>
That's my hope :)<br>
<br>
<blockquote type="cite"
cite="mid:20180611202707.gkjfsy7zq6qufkkj@norbit.de">
<pre wrap="">If we wouldn't need (to spend funds on) windows licenses to get this to fly, we
might already have public build machines. And those seems to be the current
missing bits.</pre>
</blockquote>
I read between the lines that there have been previous (PSC)
discussions about this before. And I assume the bottom line was that
donations should not be used to feed MS. So I think it might be an
opportunity of user groups or organizations to jump in and fill the
gap here. If that's the case, I will see if I can do something to
get that fixed.<br>
<br>
Matthias<br>
<br>
<br>
<blockquote type="cite"
cite="mid:20180611202707.gkjfsy7zq6qufkkj@norbit.de">
<pre wrap="">
Jürgen
</pre>
<!--'"--><br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Qgis-psc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-psc@lists.osgeo.org">Qgis-psc@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-psc">https://lists.osgeo.org/mailman/listinfo/qgis-psc</a></pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div class="moz-signature">
<title></title>
<div class="moz-signature"> <span style="text-align: left;
color: #000000; font-family: 'Verdana', sans-serif;
font-size: 10pt">Matthias Kuhn</span><br>
<a href="mailto:matthias@opengis.ch" target="_blank"> <span
style="text-align: left; color: #000000; font-family:
'Verdana', sans-serif; font-size: 8pt">matthias@opengis.ch</span>
</a><br>
<span style="text-align: left; color: #000000; font-family:
'Verdana', sans-serif; font-size: 8pt"><a
href="tel:+41764356763">+41 (0)76 435 67 63</a></span><br>
<div> <a href="http://www.opengis.ch"> <img
moz-do-not-send="false"
src="cid:part3.969EBF88.E36BF97D@opengis.ch"
alt="OPENGIS.ch Logo" width="200" height="80"></a> </div>
</div>
</div>
</div>
</body>
</html>