Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Repository information during build
Date: Mon, 12 Jan 2015 09:17:29 +0100 (CET)	[thread overview]
Message-ID: <754188306.30166927.1421050649875.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <54B2F688.9010406@gmail.com>

hey Thomas





----- Mail original -----
> Hi Bernd,
> thanks for the reply.
> 
> > TVHEADEND_VERSION = c051d0bda5b69ce61e64a97fd4a41db899dcfb53
> > TVHEADEND_SITE=$(call
> > github,tvheadend,tvheadend,$(TVHEADEND_VERSION))
> 
> In your example the version is already in the makefile. The source
>  is
> retrieved by its SHA1.
> What I wanted to do is to let the makefile always check out the
> master
> branch. I don't like to update my buildroot makefiles if the master
> branch changes its HEAD revision.
> 

This breaks one of buildroot's main selling point : reproducible builds...

The reason why BR checksout a specific ID instead of a branch name is to
make sure that two builds are exactly the same. Yes you have to manually
update your .mk when a new version is released, but you have reproducible
builds which are critical to know what you have on your plateform.

Now I understand that when you want to develop, being able to checkout a
branch is very tempting, but branches are moving targets, BR just checks
if it already has downloaded the package, and doesn't do it again if it 
finds it around. (in other word, there is no infrastructure to check 
"moving targets" like branch names)

That would be an interesting feature to add (I'm not sure how, though) but
any package that you want to upstream will have to target a specific
tag/id, because BR upstream should be reproducible...


> ... maybe I have to rethink the integration strategy. But even if, I
> really would like to have this feature....
> 
> Best regards
> Thomas
> 
> 
> 
> On 01/11/2015 07:05 PM, Bernd Kuhls wrote:
> > Thomas Ruschival <t.ruschival@gmail.com> wrote
> > in
> > news:CAAOPk_zdYo4RhifBpQq8mtBQmt4_xfmhm0rQw+ubZ9DOUDy1SQ at mail.gmail.com:
> > 
> >> I.e. how do I find out the revision of the "master" branch
> >> Buildroot used
> >> to create the tarball?
> > 
> > Hi,
> > 
> > an example:
> > http://git.buildroot.net/buildroot/tree/package/tvheadend/tvheadend.mk
> > 
> > You are looking for $(TVHEADEND_VERSION).
> > 
> > Regards, Bernd
> > 
> > _______________________________________________
> > buildroot mailing list
> > buildroot at busybox.net
> > http://lists.busybox.net/mailman/listinfo/buildroot
> > 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 

      reply	other threads:[~2015-01-12  8:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-11 20:29 [Buildroot] Repository information during build Thomas Ruschival
2015-01-11 21:05 ` Bernd Kuhls
2015-01-11 22:17   ` Thomas Ruschival
2015-01-12  8:17     ` Jeremy Rosen [this message]

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=754188306.30166927.1421050649875.JavaMail.root@openwide.fr \
    --to=jeremy.rosen@openwide.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