Number of commits found: 7

Stage 1 of gettext update.

Move gettext (0.10.35) with gettext-old
Update gettext from gettext-devel (0.10.40)
Remove gettext-devel
Fix dependencies

Stage 2 will involve upgraded gettext to 0.11 and fixing issues
Stage 3 involves a de-orbit burn sequence for gettext-old

Reviewed by:    portmgr

Use ${ECHO_CMD} instead of ${ECHO} where you mean the echo command;   the ECHO
macro is set to "echo" by default, but it is set to "true" if   make(1) is
invoked with the -s option while ECHO_CMD is always set to   the echo command.  
 

Update to 0.10.40.    

Put NO_LATEST_LINK in.    

Use bison(1) instead of yacc(1). This fixes strange problems people are having  
with various ports that use msgfmt-new (`foo.po:XYZ: syntax error'). Bump  
PORTREVISION to indicate that the update is really necessary.    

By default install only binaries with `-new' suffix applied. This provides an  
easy way to compile/use newest packages that don't build with oldest gettext  
without the headache associated with making it possible to install fill-blown  
gettext and gettext-devel on the same machine at the same time. Usually the  
following should be sufficient to fix ports that doesn't build with oldest  
gettext:    

Update to 0.10.38.    

Number of commits found: 7

12 vulnerabilities affecting 17 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities