[GRASS-dev] programming manual GRASS 7

Could be possible have a daily compilation of programming manual for GRASS 7?

There are a lots of changes and sometimes it is quite old.

--
ciao
Luca

http://gis.cri.fmach.it/delucchi/
www.lucadelu.org

On Wed, Feb 6, 2013 at 5:02 PM, Luca Delucchi <lucadeluge@gmail.com> wrote:

Could be possible have a daily compilation of programming manual for GRASS 7?

There are a lots of changes

Sure, running. It will take 30min or so from now on.

and sometimes it is quite old.

... at most 6.99 days :-), it is done every Saturday (unless broken)
by a cronjob. But it costs me nothing to rerun it manually "any" time.

cheers
Markus

2013/2/6 Markus Neteler <neteler@osgeo.org>:

... at most 6.99 days :-), it is done every Saturday (unless broken)
by a cronjob. But it costs me nothing to rerun it manually "any" time.

Instead manually, could you change in a daily cronjob?

cheers
Markus

--
ciao
Luca

http://gis.cri.fmach.it/delucchi/
www.lucadelu.org

Luca wrote:

Instead manually, could you change in a daily cronjob?

keep in mind that the shared VM that it is run on is generally
under considerable load (but not at capacity), and anything extra
on top won't help that situation. Maybe we could put a nightly
build on the adhoc VM and keep the existing one once a week?

best,
Hamish

Il giorno 07/feb/2013 04:17, “Hamish” <hamish_b@yahoo.com> ha scritto:

keep in mind that the shared VM that it is run on is generally
under considerable load (but not at capacity), and anything extra
on top won’t help that situation. Maybe we could put a nightly
build on the adhoc VM and keep the existing one once a week?

Yes this could be a good solution for my point of view.
Can you work on this task?

best,
Hamish

Thanks a lot

Ciao
Luca

On 2/7/13, Hamish <hamish_b@yahoo.com> wrote:

Luca wrote:

Instead manually, could you change in a daily cronjob?

We can change it to twice a week.

keep in mind that the shared VM that it is run on is generally
under considerable load (but not at capacity), and anything extra
on top won't help that situation.

Right, but two runs x week at readonable datime with (as usual) nice
level 10 won't harm.

Maybe we could put a nightly
build on the adhoc VM and keep the existing one once a week?

I definitely dislike this:
- info scattered in two places
- people don't understand which one is the latest
- search engine ranking gets confused
- if urgent, just generate it at home
- double maintenance efforts.

Let's have one place only please.

Markus

PS: as soon my running after the doctors ends, I can increase the
cronjob frequency. Tomorrow the progman is built anyway again.