From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4 v3] core/download: add support for git sub-modules (branch yem/git)
Date: Fri, 1 Jul 2016 11:01:16 +0200 [thread overview]
Message-ID: <cover.1467363623.git.yann.morin.1998@free.fr> (raw)
Hello All!
This little series adds support for packages coming from a git clone,
with git sub-modules.
The commit logs are pretty detailed, but roughly, it goes as thus:
- we can't get sub-modules in a bare clone, so we no longer use bare
clones, but use full clones (with a working copy);
- git-archive does not support submodules, so we generate archives
manually;
- we check out the working copy to the correct cset, then we retrieve
the submodules;
- we expose a new package variable to request sub-modules.
Changes v2 -> v3:
- added reviewd-by and tested-by tags
- typoes fixed
- rebased
Changes v1 -> v2:
- properly accept -r in the download wrapper (Aleksandar)
- split the non-bare-git and manual-archive changes in two separate
patches, as they are not semantically related
- some of my usual typoes fixed...
Regards,
Yann E. MORIN.
The following changes since commit a542d0fd55e961e3c5805f12bba490d3dcc15d33
erlang: enable compilation on mipsel (2016-07-01 00:44:36 +0200)
are available in the git repository at:
https://git.buildroot.org/~ymorin/git/buildroot
for you to fetch changes up to b9061693f4d7a2c7030190efd686c988c1278e43
core/pkg-infra: download git submodules if the package wants them (2016-07-01 10:53:32 +0200)
----------------------------------------------------------------
Yann E. MORIN (4):
support/download/git: do not use bare clones
support/download/git: do not use git archive, handle it manually
support/download/git: add support for submodules
core/pkg-infra: download git submodules if the package wants them
package/pkg-download.mk | 1 +
package/pkg-generic.mk | 8 +++++++
support/download/dl-wrapper | 7 ++++---
support/download/git | 51 ++++++++++++++++++++++++++++++++++++++-------
4 files changed, 57 insertions(+), 10 deletions(-)
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next reply other threads:[~2016-07-01 9:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 9:01 Yann E. MORIN [this message]
2016-07-01 9:01 ` [Buildroot] [PATCH 1/4 v3] support/download/git: do not use bare clones Yann E. MORIN
2016-07-02 16:42 ` Peter Korsgaard
2016-07-01 9:01 ` [Buildroot] [PATCH 2/4 v3] support/download/git: do not use git archive, handle it manually Yann E. MORIN
2016-07-02 17:08 ` Peter Korsgaard
2016-07-06 1:04 ` Ben Boeckel
2016-07-01 9:01 ` [Buildroot] [PATCH 3/4 v3] support/download/git: add support for submodules Yann E. MORIN
2016-07-02 17:09 ` Peter Korsgaard
2016-07-01 9:01 ` [Buildroot] [PATCH 4/4 v3] core/pkg-infra: download git submodules if the package wants them Yann E. MORIN
2016-07-02 17:11 ` Peter Korsgaard
2016-07-02 23:40 ` Yann E. MORIN
2016-07-02 23:55 ` Peter Korsgaard
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=cover.1467363623.git.yann.morin.1998@free.fr \
--to=yann.morin.1998@free.fr \
--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