On Sat, Nov 3, 2012 at 6:29 PM, Glynn Clements wrote:
...
> general/g.cloud:
>
> ImportError: No module named pexpect
>
> g.cloud.py imports pexpect (which isn't part of the standard library)
> but doesn't use it. cloud_ssh.py does use pexpect for scripting "ssh".
> It appears to be doing
On Fri, Nov 2, 2012 at 10:17 AM, Martin Landa wrote:
...
> btw, there are logs from WinGRASS AddOns packaging available online [1].
>
> [1] http://wingrass.fsv.cvut.cz/grass70/addons/logs/
Cool, Martin!
Markus
___
grass-dev mailing list
grass-dev@lists
Martin Landa wrote:
> > Relegating something to add-ons is a reliable way to reduce the amount
> > of developer oversight it gets. E.g. currently you can't just "make"
> > the add-ons/grass7 directory (it lacks a Makefile), so most developers
> > won't even try to compile it. If the modules were
On 2 November 2012 22:35, Glynn Clements wrote:
>
> Yann Chemin wrote:
>
> > > r53636 fixes a couple of issues with the r.in.wms2 and v.in.wfs2
> > > Makefiles. From the add-ons/grass7 directory, you can do e.g.:
> > >
> > > make MODULE_TOPDIR=$GISBASE
> > >
> >
> > Thanks, including addo
Yann Chemin wrote:
> > r53636 fixes a couple of issues with the r.in.wms2 and v.in.wfs2
> > Makefiles. From the add-ons/grass7 directory, you can do e.g.:
> >
> > make MODULE_TOPDIR=$GISBASE
> >
>
> Thanks, including addons SVN in my daily compile... How could we auto-load
> those additi
Hi,
2012/10/31 Glynn Clements :
> Relegating something to add-ons is a reliable way to reduce the amount
> of developer oversight it gets. E.g. currently you can't just "make"
> the add-ons/grass7 directory (it lacks a Makefile), so most developers
> won't even try to compile it. If the modules w
On 1 November 2012 23:34, Glynn Clements wrote:
>
> Markus Neteler wrote:
>
> > > Relegating something to add-ons is a reliable way to reduce the amount
> > > of developer oversight it gets. E.g. currently you can't just "make"
> > > the add-ons/grass7 directory (it lacks a Makefile),
> >
> > Now
Markus Neteler wrote:
> > Relegating something to add-ons is a reliable way to reduce the amount
> > of developer oversight it gets. E.g. currently you can't just "make"
> > the add-ons/grass7 directory (it lacks a Makefile),
>
> Now there is.
r53636 fixes a couple of issues with the r.in.wms2
On 1 November 2012 12:29, Markus Neteler wrote:
> On Wed, Oct 31, 2012 at 10:33 PM, Glynn Clements
> wrote:
> >
> > Moritz Lennert wrote:
> >
> >> > I suggest that modules should not simply be moved from addons to
> >> > trunk, but that a developer has a close look at a module including
> >> > t
On Wed, Oct 31, 2012 at 10:33 PM, Glynn Clements
wrote:
>
> Moritz Lennert wrote:
>
>> > I suggest that modules should not simply be moved from addons to
>> > trunk, but that a developer has a close look at a module including
>> > testing before moving it to trunk.
>>
>> +1, but I see Martin's poi
Hi Glynn,
I would like to have that kind of Makefile,
so I can build all grass add-ons related to GRASS 7 SVN without changing
anything in the structure of the SVN
Could anyone help us to get somewhere near to that effect, even if we would
need a configure option like --build-addons-dir=../grass-
Moritz Lennert wrote:
> > I suggest that modules should not simply be moved from addons to
> > trunk, but that a developer has a close look at a module including
> > testing before moving it to trunk.
>
> +1, but I see Martin's point about lack of dev power. So the trade-off
> has to be between
On 31/10/12 10:47, Markus Metz wrote:
On Wed, Oct 31, 2012 at 9:31 AM, Moritz Lennert
wrote:
On 31/10/12 09:15, Markus Metz wrote:
On Wed, Oct 31, 2012 at 5:58 AM, Yann Chemin
wrote:
On 31 October 2012 02:25, Helena Mitasova wrote:
Maybe PSC should have some mechanism to decide on w
On Wed, Oct 31, 2012 at 9:31 AM, Moritz Lennert
wrote:
> On 31/10/12 09:15, Markus Metz wrote:
>>
>> On Wed, Oct 31, 2012 at 5:58 AM, Yann Chemin
>> wrote:
>>>
>>> On 31 October 2012 02:25, Helena Mitasova wrote:
>
Maybe PSC should have some mechanism to decide on which add-ons to move
On 31/10/12 09:15, Markus Metz wrote:
On Wed, Oct 31, 2012 at 5:58 AM, Yann Chemin wrote:
On 31 October 2012 02:25, Helena Mitasova wrote:
I agree with Glynn and Ben,
when working with students on 50+ different projects it is really great to
have everything
in one package and not to worry
On Wed, Oct 31, 2012 at 5:58 AM, Yann Chemin wrote:
>
>
> On 31 October 2012 02:25, Helena Mitasova wrote:
>>
>> I agree with Glynn and Ben,
>> when working with students on 50+ different projects it is really great to
>> have everything
>> in one package and not to worry about which additional t
On 31 October 2012 02:25, Helena Mitasova wrote:
> I agree with Glynn and Ben,
> when working with students on 50+ different projects it is really great to
> have everything
> in one package and not to worry about which additional tool to install and
> whether it will work with the latest release
Hi,
I'm with Helena, Glynn and Ben,
I think that having many module in one package is better for users that do
not have to take care of anything else.
If I have GRASS installed, I can find anything there (without need
of searching for additional modules that are not found in the manuals!).
And the
Hi,
2012/10/30 Helena Mitasova :
> I agree with Glynn and Ben,
> when working with students on 50+ different projects it is really great to
> have everything
> in one package and not to worry about which additional tool to install and
> whether it will work with the latest release.
> We used to
I agree with Glynn and Ben,
when working with students on 50+ different projects it is really great to have
everything
in one package and not to worry about which additional tool to install and
whether it will work with the latest release.
We used to have the code split into core, alpha and sever
Martin Landa wrote:
> > as a regular user of MODIS, I would like to call other MODIS users to
> > express interest to include r.modis into GRASS 7 SVN.
>
> we cannot extend number of modules in trunk forever. Probably some
> modules should be reviewed and moved to addons.
Why?
Keeping modules
ng of this communication is strictly
prohibited.
From: grass-dev-boun...@lists.osgeo.org
[mailto:grass-dev-boun...@lists.osgeo.org] On Behalf Of Yann Chemin
Sent: Tuesday, October 30, 2012 3:43 AM
To: Martin Landa
Cc: GRASS developers list
Subject: Re: [GRASS-dev] r.modis in GRASS 7 trunk
Hi Martin,
Hi Martin,
It would be good to return modules that are less frequently used to add-ons.
Yann
--
Yann Chemin
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Hi,
2012/10/30 Benjamin Ducke :
> What's the difference between having 300 or 500
> modules in the base distribution? GRASS has the
> file layout required to scale up to this size
> easily, and each individual module is small and
> lean. Even if we were to triple the number of
> modules in the bas
I would like to express a different point of view.
One of the nice things about GRASS in its current
form is that one download will get you hundreds
of modules without having to worry about installing
add-ons.
What's the difference between having 300 or 500
modules in the base distribution? GRAS
Hi Martin,
I have no worries, since I do load modules directly. I am worried about the
learning curve for Windows-bound students in need of MODIS images, but not
comfortable with GRASS GIS yet.
But this is an old story coming back,
I am all for reducing significantly the number of modules in GRA
Hi,
2012/10/30 Yann Chemin :
> as a regular user of MODIS, I would like to call other MODIS users to
> express interest to include r.modis into GRASS 7 SVN.
we cannot extend number of modules in trunk forever. Probably some
modules should be reviewed and moved to addons.
Do you have any problem
On Tuesday 30 of October 2012 11:31:49 Yann Chemin wrote:
> Hi list,
>
> as a regular user of MODIS, I would like to call other MODIS users to
> express interest to include r.modis into GRASS 7 SVN.
Herewith I express my HUGE interest in the integration of r.modis into GRASS 7
SVN.
Thank you f
Hi list,
as a regular user of MODIS, I would like to call other MODIS users to
express interest to include r.modis into GRASS 7 SVN.
Cheers,
Yann
--
Yann Chemin
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listin
29 matches
Mail list logo
