[GRASS-dev] some GRASS source and packaging observations and questions

[William Kyngesburye]

While working on an Xcode project for GRASS (almost ready, just needs  
some testing), I came across a few oddities, and have a couple  
questions.  I submitted a couple bugs, these are leftovers that I'm  
not sure about their bug-ness.


- r.li - its library is named libr_li, or the full file name:  
liblibr_li.[libext].  This doesn't really fit in with the libgrass_ 
[foo].[libext] naming of GRASS.

- r3.in|out.v5d - these are built by default, but I noticed in the  
source that they are big-endian-only, with comments that little- 
endian byte-swapping code is needed.  It looks like there was a start  
at it, as binio.c accepts a -DLITTLE flag, and a couple places (but  
not all) have byte-swap code.

If these are in such a state, they probably shouldn't be built by  
default.

- bin/scripts - I'm curious if there is a practical reason to  
separate compiled progs and scripts into bin and scripts folders?   
Maybe some have the scripts folder name hardcoded in them for some  
reason, or maybe in the GUI?

Basically they are all executables, and it adds another path item  
needed in the PATH env.  (And I need to deal with a possible/rare  
case-sensitivity problem in a Mac app package between 'scripts' and  
'Scripts'.)

-----
William Kyngesburye <kyngchaos at kyngchaos.com>
http://www.kyngchaos.com/

"Mon Dieu! but they are all alike.  Cheating, murdering, lying,  
fighting, and all for things that the beasts of the jungle would not  
deign to possess - money to purchase the effeminate pleasures of  
weaklings.  And yet withal bound down by silly customs that make them  
slaves to their unhappy lot while firm in the belief that they be the  
lords of creation enjoying the only real pleasures of existence....

- the wisdom of Tarzan