[GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support

[Stefan Blumentrath]

Hi,

This does not seem to be trivial, so I do not want to complicate.
Personally, I would just be worried that splitting up AddOns in submodules / different repos might lead to incoherence and maintenance issues (esp. updating and improving addons in a community effort). So, from my addon-dev perspective this does not sound very appealing...

(As a non-windows user) I read that also the addon situation for Windows is not optimal, but since we do have an auto-build in place could`nt we "just" expand the procedure to provide code of individual addons on a server somewhere (for user convenience).

People interested in accessing addon code instantly should be able to deal with the full addon repo. Maybe splitting up grass7 and grass6 addons in different repos could reduce the pain a bit?

Cheers
Stefan

-----Original Message-----
From: grass-dev <grass-dev-bounces at lists.osgeo.org> On Behalf Of Sebastiaan Couwenberg
Sent: fredag 6. september 2019 06:53
To: grass-dev at lists.osgeo.org
Subject: Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support

On 9/6/19 5:18 AM, Vaclav Petras wrote:
> On Thu, Sep 5, 2019 at 7:18 AM Martin Landa <landa.martin at gmail.com> wrote:
>> čt 5. 9. 2019 v 12:48 odesílatel Sebastiaan Couwenberg 
>> <sebastic at xs4all.nl> napsal:
>>>> that's wrong, g.extension is using 'svn export' (for official repo).
>>>
>>> Using `svn export` for git repositories makes no sense/is a horrible
>> hack.
>>
>> I agree, so please suggest better solution to avoid that g.extension 
>> will clone whole repository to install only single addon. Personally 
>> I have no better idea than to use `svn export`.
>>
> 
> Please also note that the latest pre-Git/GitHub g.extension was 
> primarily not using Subversion, but it was using a nice Trac feature 
> which allowed to download a zipped subdirectory of the repo, so 
> Subversion was not a must-have dependency. The idea was to get rid of 
> build tool dependencies for Python modules as well resulting in no dev 
> packages needed for Python modules on Linux while possibly getting 
> arbitrary Python GRASS module code on Windows from Trac or, e.g., from 
> GitHub which supports downloading of a
> (whole) repo (without submodules) as a zip file.

`git archive` can create zip or tar.gz files from a repo, with individual addon repos this can replace the Trac feature.

If you want to get rid of the build tools on the users system, provide the archive creation as a service on e.g. grass.osgeo.org.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1 _______________________________________________
grass-dev mailing list
grass-dev at lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev