[GRASS-dev] python scripts in grass6

[Martin Landa]

Hi,

2009/7/7 Glynn Clements <glynn at gclements.plus.com>:
>> >> Probably I was unclear, I would like just to avoid having two separate
>> >> Makefiles for one Python script, one for GRASS7 with `PGM=module` and
>> >> the second for GRASS6 with `PGM=module.py`. Nothing more.
>> >
>> > Regardless, make needs to know which file it's supposed to be
>> > creating. If you want to autodect this, it requires new code; current
>> > or previous practice in GRASS 7 won't help.
>>
>> Probably it would make sense to add support to the building system for
>> shell scripts again - some users have a lot of such scripts.
>
> Users scripts aren't relevant to the GRASS build system.

Probably users are important for us ;-)

>> Then PGM should always contain file extension.
>
> No, because the file extension is removed on Unix, and it doesn't
> appear in the name of the manpage or HTML file. PGM is the *name* of
> the module or script, not necessarily its filename.

That is what I was asking for. So how to avoid python file extension
in Makefiles for GRASS 6. Currently, e.g.

PGM=v.krige

fails, must be

PGM=v.krige.py

Thanks, Martin

-- 
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa