From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andrew Bradford <andrew@bradfordembedded.com>,
openembedded-core@lists.openembedded.org
Cc: Andrew Bradford <andrew.bradford@kodakalaris.com>
Subject: Re: [PATCH 2/3] bitbake.conf: Add P4DIR and FETCHCMD_p4
Date: Thu, 02 Jun 2016 16:56:33 +0100 [thread overview]
Message-ID: <1464882993.13979.7.camel@linuxfoundation.org> (raw)
In-Reply-To: <1464205571-26293-3-git-send-email-andrew@bradfordembedded.com>
On Wed, 2016-05-25 at 15:46 -0400, Andrew Bradford wrote:
> From: Andrew Bradford <andrew.bradford@kodakalaris.com>
>
> So that perforce fetching can work more like the other source control
> system fetchers.
>
> Signed-off-by: Andrew Bradford <andrew.bradford@kodakalaris.com>
> ---
> meta/conf/bitbake.conf | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index acef30b..1aa1d37 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -339,6 +339,7 @@ SVNDIR = "${CO_DIR}/svn"
> GITDIR = "${CO_DIR}/git2"
> BZRDIR = "${CO_DIR}/bzr"
> HGDIR = "${CO_DIR}/hg"
> +P4DIR = "${CO_DIR}/p4"
>
> STAMPS_DIR ?= "${TMPDIR}/stamps"
> STAMP =
> "${STAMPS_DIR}/${MULTIMACH_TARGET_SYS}/${PN}/${EXTENDPE}${PV}-${PR}"
> @@ -618,6 +619,7 @@ FETCHCMD_cvs = "/usr/bin/env cvs"
> FETCHCMD_wget = "/usr/bin/env wget -t 2 -T 30 -nv --passive-ftp --no
> -check-certificate"
> FETCHCMD_bzr = "/usr/bin/env bzr"
> FETCHCMD_hg = "/usr/bin/env hg"
> +FETCHCMD_p4 = "/usr/bin/env p4"
I've kind of been hoping we could move to a model where the fetcher has
sane defaults and we don't need to change anything in bitbake.conf
unless the user has some need to customise.
The FETCHCMD is easy to do that for, the P4DIR is slightly harder since
it means teaching the fetcher about CO_DIR which bitbake currently
knows nothing about. It may be worth dropping the notion of CO_DIR and
making the default ${DL_DIR}/p4 which bitbake does know about and
making the other fetchers match which such defaults?
Cheers,
Richard
next prev parent reply other threads:[~2016-06-02 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 19:46 [PATCH 0/3] Setup for bitbake perforce fetcher changes Andrew Bradford
2016-05-25 19:46 ` [PATCH 1/3] oe-buildenv-internal: Add P4CONFIG to BB_ENV_EXTRAWHITE_OE Andrew Bradford
2016-06-02 15:53 ` Richard Purdie
2016-05-25 19:46 ` [PATCH 2/3] bitbake.conf: Add P4DIR and FETCHCMD_p4 Andrew Bradford
2016-06-02 15:56 ` Richard Purdie [this message]
2016-06-02 17:06 ` Andrew Bradford
2016-05-25 19:46 ` [PATCH 3/3] base.bbclass: p4 fetcher supports srcrev Andrew Bradford
2016-06-17 12:52 ` Andrew Bradford
2016-06-17 16:08 ` Richard Purdie
2016-06-02 13:41 ` [PATCH 0/3] Setup for bitbake perforce fetcher changes Andrew Bradford
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=1464882993.13979.7.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=andrew.bradford@kodakalaris.com \
--cc=andrew@bradfordembedded.com \
--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