From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/5] Introduce alternative archive format
Date: Sun, 29 Nov 2015 22:05:22 +0100 [thread overview]
Message-ID: <565B6892.9040706@mind.be> (raw)
In-Reply-To: <1447929366-8972-1-git-send-email-jezz@sysmic.org>
On 19-11-15 11:36, J?r?me Pouiller wrote:
> Hello,
>
> As suggested by Arnout [1], this series provide an alternative archive
> format. This new format contains a shallowed version of upstream
> repository. This format is a little bigger and a little longer to
> create but it allow a better workflow with upstream. I describe some
> good practice in patch 2.
The use case I had in mind with [1] was not so much working with upstream (for
that, OVERRIDE_SRCDIR is much more appropriate), but rather to make it cheaper
to get different upstream versions. Particularly for linux repositories, if you
downloaded one of them, you can reuse a large part of it when you get another
version. When you can do a shallow clone there is often not so much to gain from
that, but in many of our defconfigs a shallow clone is not possible because we
specify a sha. In that case, an incremental download really saves a lot of time.
Regards,
Arnout
>
> Notice projects hosted by github don't yet benefit of this feature
> since I have not found any elegant way to do it :-(.
>
> During my tests, I have noticed current shallow clone is mostly broken
> (at least with git < 2.5 [2]). Indeed, shallow clone only work with
> symbolic references (HEAD, a tag or a branch). However, we avoid use of
> symbolic references in VERSION.
>
> [1] http://lists.busybox.net/pipermail/buildroot/2015-November/144296.html
> [2] http://stackoverflow.com/a/30701724/301717
>
>
> J?r?me Pouiller (5):
> pkg-download: do not test SITE_METHOD
> download/git: allow to create archives containing shallowed git repos
> pkg-generic: allow to populate build directory from a git archive
> pkg-generic: provide an option to use git archives
> pkg-generic: tag sources if git is used
>
> Config.in | 13 +++++++++++
> package/pkg-download.mk | 7 +-----
> package/pkg-generic.mk | 60 ++++++++++++++++++++++++++++++++++---------------
> support/download/git | 30 ++++++++++++++++++++++---
> 4 files changed, 83 insertions(+), 27 deletions(-)
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-11-29 21:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 10:36 [Buildroot] [PATCH 0/5] Introduce alternative archive format Jérôme Pouiller
2015-11-19 10:36 ` [Buildroot] [PATCH 1/5] pkg-download: do not test SITE_METHOD Jérôme Pouiller
2015-11-29 17:57 ` Yann E. MORIN
2015-12-18 9:08 ` Thomas Petazzoni
2015-11-19 10:36 ` [Buildroot] [PATCH 2/5] download/git: allow to create archives containing shallowed git repos Jérôme Pouiller
2015-11-19 10:36 ` [Buildroot] [PATCH 3/5] pkg-generic: allow to populate build directory from a git archive Jérôme Pouiller
2015-11-19 10:36 ` [Buildroot] [PATCH 4/5] pkg-generic: provide an option to use git archives Jérôme Pouiller
2015-11-19 10:36 ` [Buildroot] [PATCH 5/5] pkg-generic: tag sources if git is used Jérôme Pouiller
2015-11-19 12:02 ` [Buildroot] [PATCH 0/5] Introduce alternative archive format Thomas Petazzoni
2015-11-23 9:54 ` Jérôme Pouiller
2015-11-29 18:02 ` Yann E. MORIN
2015-11-30 12:32 ` Jérôme Pouiller
2015-11-29 21:05 ` Arnout Vandecappelle [this message]
2015-12-29 21:36 ` Yann E. MORIN
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=565B6892.9040706@mind.be \
--to=arnout@mind.be \
--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 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.