[GRASS-dev] Testing an add-on from sandbox before moving to grass-addons

Vaclav Petras wenzeslaus at gmail.com
Wed May 6 11:42:04 PDT 2015


On Wed, May 6, 2015 at 8:41 AM, Markus Neteler <neteler at osgeo.org> wrote:
>
> On Wed, May 6, 2015 at 2:44 PM, Nikos Alexandris
> <nik at nikosalexandris.net> wrote:
> > * Vaclav Petras <wenzeslaus at gmail.com> [2015-05-05 08:51:06 -0400]:
> > So, you folks keep a complete copy of it locally?
>
> Yes sure.
>
> > Isn't it big?
>
> No, 154MB.

This is size of "one" source code (119.3 MB for pure trunk, includes po
files which are over 40 MB) but the whole GRASS SVN (12.3 GB) I need for
moving things between sandbox, addons and main code. I don't know about
better way (but I'm interested if there is some). The size is one of the
disadvantages of Subversion as compared to Git, each tag is a separate copy
(grass/tags has 7.2 GB). On the other hand, if we would be using Git,
sandbox, addons and main source code would be probably separate
repositories, the moving file (including its history) would be a bigger
challenge (I believe solvable but not as easy as `svn checkout
everything`+`svn mv ...`).

But yes, I'm definitively using the advantage of having small source code,
I have several trunk checkouts on my machine.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20150506/ec18de5d/attachment.html>


More information about the grass-dev mailing list