Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: FETCHCMD versus FETCHCOMMAND
Date: Mon, 09 Jul 2012 17:58:02 +0100	[thread overview]
Message-ID: <1341853082.8066.34.camel@ted> (raw)
In-Reply-To: <alpine.DEB.2.02.1207070629090.18029@oneiric>

On Sat, 2012-07-07 at 06:33 -0400, Robert P. J. Day wrote:
> just noticed the following as i was still poking around with
> fetchers:
> 
> $ grep -r FETCHCMD * | grep -v pyc
> bitbake/lib/bb/fetch2/hg.py:        basecmd = data.expand('${FETCHCMD_hg}', d)
> bitbake/lib/bb/fetch2/svn.py:        ud.basecmd = d.getVar('FETCHCMD_svn', True)
> bitbake/lib/bb/fetch2/osc.py:        basecmd = data.expand('${FETCHCMD_osc}', d)
> bitbake/lib/bb/fetch2/git.py:        ud.basecmd = data.getVar("FETCHCMD_git", d, True) or "git"
> bitbake/lib/bb/fetch2/git.py:        basecmd = data.getVar("FETCHCMD_git", d, True) or "git"
> bitbake/lib/bb/fetch2/git.py:        basecmd = data.getVar("FETCHCMD_git", d, True) or "git"
> bitbake/lib/bb/fetch2/bzr.py:        basecmd = data.expand('${FETCHCMD_bzr}', d)
> bitbake/ChangeLog:	  (requires new FETCHCMD_svn definition in bitbake.conf)
> meta/conf/bitbake.conf:FETCHCMD_svn = "/usr/bin/env svn"
> meta/conf/bitbake.conf:FETCHCMD_cvs = "/usr/bin/env cvs"
> meta/conf/bitbake.conf:FETCHCMD_wget = "/usr/bin/env wget -t 2 -T 30 -nv --no-check-certificate"
> meta/conf/bitbake.conf:FETCHCMD_bzr = "/usr/bin/env bzr"
> meta/conf/bitbake.conf:FETCHCMD_hg = "/usr/bin/env hg"
> $
> 
>   i can see that FETCHCMD represent the "base" fetch command for each
> fetcher, i also notice that there isn't a perfect correspondence
> between the fetchers and bitbake.conf.
> 
>   for example, there's no definition of FETCHCMD_osc even though
> osc.py checks for it.  conversely, bitbake.conf sets FETCHCMD_cvs even
> though the cvs.py fetcher never bothers to check it.
> 
>   nothing wrong with any of that, just an observation about
> consistency.

Thanks for the reminder. The idea was to drop the COMMAND versions in
favour of the CMD ones. I've just sent out a series of patches which
would complete that work.

We're probably heading to a point where the fetchers have sane defaults
encoded and we remove the bitbake.conf settings entirely for the default
case just allowing the user to override if ever needed.

Cheers,

Richard




      reply	other threads:[~2012-07-09 17:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-07 10:33 FETCHCMD versus FETCHCOMMAND Robert P. J. Day
2012-07-09 16:58 ` Richard Purdie [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1341853082.8066.34.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox