From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] About Git through SSH
Date: Sat, 4 Sep 2010 18:58:31 +0200 [thread overview]
Message-ID: <20100904185831.78af11ca@surf> (raw)
In-Reply-To: <000c01cb4bd0$088c14f0$19a43ed0$@pauljones.id.au>
On Sat, 4 Sep 2010 11:25:15 +1000
"Paul Jones" <paul@pauljones.id.au> wrote:
> By the way, why does the source get converted to a tar.gz after the
> git tree is cloned? It's quite annoying because to rebuild the
> package you have to delete the tar.gz file as well as the build
> directory to force downloading of the latest source.
I agree that this is not optimal, but this is the solution that best
follows the way Buildroot works currently. If we don't do this, where
should Buildroot do the clone ? In the $(BUILD_DIR) which gets deleted
by make clean ? Or in $(DL_DIR) in a directory form and then we need to
do a "cp" to the $(BUILD_DIR) when doing the build ?
In a second step, it'd be nice to be able to tell Buildroot that for
this or that package, instead of being responsible for
downloading/extracting it, it should just grab it from a given
location. This is, IMHO, a change needed to make Buildroot more usable
during the development phase, but it needs quite a bit of reflection
and discussion.
Cheers,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-09-04 16:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 10:09 [Buildroot] [RESEND/PATCH] Git/Svn downloaders Maxime Petazzoni
2010-09-02 10:09 ` [Buildroot] [PATCH 1/8] Remove the spider feature Maxime Petazzoni
2010-09-02 10:09 ` [Buildroot] [PATCH 2/8] Cleanup the VCS commands configuration Maxime Petazzoni
2010-09-02 10:09 ` [Buildroot] [PATCH 3/8] Update defconfigs with new VCS config options Maxime Petazzoni
2010-09-02 10:09 ` [Buildroot] [PATCH 4/8] Implement basic non-wget download methods Maxime Petazzoni
2010-09-02 12:37 ` Michael S. Zick
2010-09-02 12:50 ` Thomas Petazzoni
2010-09-03 12:30 ` Michael S. Zick
2010-09-03 13:04 ` [Buildroot] About Git through SSH Thomas Petazzoni
2010-09-03 14:37 ` Michael S. Zick
2010-09-03 15:03 ` Thomas Petazzoni
2010-09-03 15:59 ` Michael S. Zick
2010-09-04 1:25 ` Paul Jones
2010-09-04 16:58 ` Thomas Petazzoni [this message]
2010-09-05 1:50 ` Paul Jones
2010-09-05 3:05 ` James J. Dines
2010-09-05 3:12 ` James J. Dines
2010-09-02 10:09 ` [Buildroot] [PATCH 5/8] Use the normal download method for Tremor Maxime Petazzoni
2010-09-02 10:09 ` [Buildroot] [PATCH 6/8] Use the normal download method for libsvgtiny Maxime Petazzoni
2010-09-02 10:09 ` [Buildroot] [PATCH 7/8] Re-implement the source-check and external-deps targets Maxime Petazzoni
2010-09-02 10:19 ` [Buildroot] Missed a bug Maxime Petazzoni
2010-09-02 10:19 ` [Buildroot] [PATCH 7/8] Re-implement the source-check and external-deps targets Maxime Petazzoni
2010-09-02 10:24 ` Thomas Petazzoni
2010-09-02 10:31 ` Maxime Petazzoni
2010-09-02 10:09 ` [Buildroot] [PATCH 8/8] Revert "Makefile.package.in: allow packages to override download step" Maxime Petazzoni
2010-09-02 10:51 ` Thomas Petazzoni
2010-09-02 10:59 ` Maxime Petazzoni
2010-09-02 12:03 ` [Buildroot] [RESEND/PATCH] Git/Svn downloaders Thomas Petazzoni
2010-09-07 14:58 ` Maxime Petazzoni
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=20100904185831.78af11ca@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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