From: Gary Thomas <gary@mlbassoc.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Poky <poky@lists.pokylinux.org>
Subject: Re: git tarballs gone?
Date: Thu, 10 Feb 2011 07:46:12 -0700 [thread overview]
Message-ID: <4D53FA34.4000105@mlbassoc.com> (raw)
In-Reply-To: <1297301826.20543.1722.camel@rex>
On 02/09/2011 06:37 PM, Richard Purdie wrote:
> On Wed, 2011-02-09 at 18:13 -0700, Gary Thomas wrote:
>> I just noticed that with the new fetcher, git tarballs are
>> no longer being created.
>> * Is this expected?
>> * Can it be [re]enabled? This is a great help to me so I
>> can distribute pre-staged sources to my customers. Tarballs
>> are much more convenient than .git repositories.
>
> Its expected, just set BB_GENERATE_MIRROR_TARBALLS = "1" in local.conf
> to generate them if you need them.
>
> As standard the average user doesn't need/use/want them and the fetcher
> no longer needs them so we don't generate them by default any more.
What would I need to do to get them generated? Here's what I
tried (which did not work):
* I noticed that my build used git.pokylinux.org.matchbox-terminal, so
... set BB_GENERATE_MIRROR_TARBALLS in local.conf
% bitbake matchbox-terminal -c clean
% rm -f sstate-cache/*matchbox-terminal*
% bitbake matchbox-terminal
It seemed happy to use the stored GIT in downloads/git2/git.pokylinux.org.matchbox-terminal,
but did not generate a tarball during the process.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-02-10 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 1:13 git tarballs gone? Gary Thomas
2011-02-10 1:22 ` Saul Wold
2011-02-10 1:37 ` Richard Purdie
2011-02-10 14:46 ` Gary Thomas [this message]
2011-02-10 15:13 ` Richard Purdie
2011-02-10 15:33 ` Richard Purdie
2011-02-10 15:40 ` Gary Thomas
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=4D53FA34.4000105@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=poky@lists.pokylinux.org \
--cc=richard.purdie@linuxfoundation.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