From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] feature or pebkac
Date: Thu, 29 Aug 2013 21:05:53 +0200 [thread overview]
Message-ID: <521F9B91.7040903@mind.be> (raw)
In-Reply-To: <20130829111708.c603e5bf976541d3abd3a43a@lavabit.com>
On 08/29/13 20:17, rh wrote:
> I have found that changing the url for a custom kernel tar ball does not
> trigger a rebuild when running make. I have removed linux-custom dir
> and then make fetches the new tar ball and rebuilds.
That's right. Buildroot doesn't try to be perfect for rebuilds when the
configuration changes - but if it is simple to fix, patches are welcome!
> I have found that when I specify a kernel git repo that I get the whole
> repo.
If you specify a tag, then it should do a shallow clone.
> But I don't need all that and I now use --single-branch argument
> to git clone followed by git archive to create a tar ball.
That's a great idea! However, this option is only available since git
1.7.10 and I think that many production environments still have older git
versions.
> I do this for repos
> that have no snapshot or tar ball. I thought that this feature might exist
> but I couldn't find it. Maybe I can edit some config manually?
There's no config for that, it's part of the core infrastructure.
Regards,
Arnout
>
> Would it be a useful feature for others if it's not there now?
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
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: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next parent reply other threads:[~2013-08-29 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130829111708.c603e5bf976541d3abd3a43a@lavabit.com>
2013-08-29 19:05 ` Arnout Vandecappelle [this message]
2013-08-29 20:25 ` [Buildroot] feature or pebkac Thomas De Schampheleire
[not found] ` <20130829153937.f53bdce09f0a855807dd0a5d@lavabit.com>
2013-08-30 7:35 ` Thomas De Schampheleire
2013-08-30 7:58 ` Thomas Petazzoni
2013-08-30 8:22 ` Arnout Vandecappelle
2013-08-30 8:30 ` Thomas Petazzoni
2013-08-30 12:45 ` 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=521F9B91.7040903@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox