[bitbake-devel] current status of "FETCHCOMMAND_" vs "FETCHCMD_"?

[Robert P. J. Day]

  a few months back, i asked about the distinction between the two
forms of FETCH variables, and richard purdie answered thusly:

http://lists.linuxtogo.org/pipermail/openembedded-core/2012-July/025311.html

however, there are still settings of some FETCHCOMMAND_ variables in
bitbake's bitbake.conf file:

FETCHCOMMAND_cvs = "/usr/bin/env cvs -d${CVSROOT} co ${CVSCOOPTS} ${CVSMODULE}"
FETCHCOMMAND_svn = "/usr/bin/env svn co ${SVNCOOPTS} ${SVNROOT} ${SVNMODULE}"
FETCHCOMMAND_wget = "/usr/bin/env wget -t 5 --passive-ftp -P ${DL_DIR} ${URI}"

and even usage of one that doesn't even appear to be set:

$ grep -r FETCHCOMMAND_p4 *
Binary file lib/bb/fetch2/perforce.pyc matches
lib/bb/fetch2/perforce.py:        p4cmd = data.getVar('FETCHCOMMAND_p4', d, True)
$

  is there still a plan to migrate everything to the FETCHCMD_
variations?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================