[bitbake-devel] are the fetch-related variables in bitbake's bitbake.conf of any value?

[Robert P. J. Day]

On Fri, 20 Jun 2014, Christopher Larson wrote:

>
> On Fri, Jun 20, 2014 at 9:00 AM, Robert P. J. Day <rpjday at crashcourse.ca> wrote:
>
>   more specific question related to my earlier post -- is there any
> value whatever in the variables in bitbake's bitbake.conf file of the
> form:
>
>   FETCHCOMMAND*
>   RESUMECOMMAND*
>   UPDATECOMMAND*
>   MKTEMP*CMD
>
> nothing seems to use any of those. can they all just be deleted?
> certainly, the FETCHCOMMAND* variables have been superseded by the
> FETCHCMD* variables, no? i don't know about the remainder of them.
>
> As far as I know, as you say, those were deprecated in favor of the
> FETCHCMD vars, so can almost certainly be dropped.

  one more question before i submit a patch to do some cleaning.
AFAICT, the bitbake.conf settings for RESUMECOMMAND* and
UPDATECOMMAND* variables can be removed as well since nothing in
bitbake refers to those variables, and it seems logical that bitbake
should not be setting variables that it doesn't directly use in some
way.

  however, i'm puzzled by this from the bitbake codebase:

$ grep -r "MKTEMP.*CMD" *
conf/bitbake.conf:MKTEMPCMD = "mktemp -q ${TMPBASE}"
conf/bitbake.conf:MKTEMPDIRCMD = "mktemp -d -q ${TMPBASE}"
lib/toaster/orm/fixtures/orm_views_testdata.json:        "variable_name": "MKTEMPCMD"
lib/toaster/orm/fixtures/orm_views_testdata.json:        "variable_name": "MKTEMPDIRCMD"
$

  so the only reference to the MKTEMP-related variables are in the
toaster directory in some .json files. what does that mean? if one
wanted to remove the MKTEMP* variables, would one also have to adjust
those .json files accordingly?

rday

-- 

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

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