[GRASS-dev] [GRASS GIS] #1952: wingrass: please add tac and seq to extrabin

[GRASS GIS]

#1952: wingrass: please add tac and seq to extrabin
-------------------------+--------------------------------------------------
 Reporter:  hamish       |       Owner:  grass-dev@…              
     Type:  enhancement  |      Status:  new                      
 Priority:  normal       |   Milestone:  6.4.3                    
Component:  Packaging    |     Version:  svn-develbranch6         
 Keywords:  wingrass     |    Platform:  MSWindows XP             
      Cpu:  x86-32       |  
-------------------------+--------------------------------------------------

Comment(by wenzeslaus):

 Replying to [comment:11 glynn]:
 > Replying to [ticket:1952 hamish]:
 >
 > > tac.exe and seq.exe are no longer shipped with wingrass. (I'm not sure
 if tac ever was)
 >
 > tac and seq aren't specified by POSIX. Any scripts which use them should
 be modified to work without them.
 >
 > Not only is seq trivial to implement as a shell function, I can't find
 anything which actually uses it.
 >
 > The only user of tac appears to be v.in.mapgen, which provides its own
 implementation (using awk) as a fallback.
 >

 I would expect that users wants to use them in their own scripts, or their
 might be used in addons. The fact is that their are used in manual,
 however each just once/twice:

 {{{
 dist.../docs/html $ egrep -Irn "tac " .
 ./m.cogo.html:169:    m.cogo -l in=cogo.dat | tac | awk '
 ./m.cogo.html:172:       END { printf("L %d\n", R) }' | tac | \
 }}}

 {{{
 dist.../docs/html $ egrep -Irn "seq " .
 ./d.out.gpsdrive.html:139:for i in `seq 1 $panels_ew`;
 ./d.out.gpsdrive.html:142:  for j in `seq 1 $iter`;
 }}}

 I would just ignore these two.

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/1952#comment:12>
GRASS GIS <http://grass.osgeo.org>