From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: bitbake 1.8 badness in using same git for different bb
Date: Mon, 01 Sep 2008 13:09:11 +0200 [thread overview]
Message-ID: <g9gign$j27$1@ger.gmane.org> (raw)
In-Reply-To: <20080901105009.GC24372@buddha.tw.openmoko.com>
John Lee wrote:
> hi,
>
> in bitbake 1.8 git.py, _revision_key returns ud.host + ud.path, that
> means if two bb share the same git dir, the _revision_key will be the
> same. that will cause problem if you use AUTOREV. the local count
> will keep increasing everytime you call bitbake.
Related to this: You can't do something like:
SRC_URI = "git://ffmpeg;protocol=git \
git://mplayer/swscale;protocol=git"
since both checkouts will use the 'git' dir in ${WORKDIR}.
regards,
Koen
next prev parent reply other threads:[~2008-09-01 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 10:50 bitbake 1.8 badness in using same git for different bb John Lee
2008-09-01 11:09 ` Koen Kooi [this message]
2008-09-02 13:47 ` Holger Freyther
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='g9gign$j27$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.