Skip to contentSkip to conversation

Feature request - pull sources from repose

Buildroot James Hanley 3 participants 6 messages Jul 7, 2011 – Jul 8, 2011

lore
Share & tools
lore
#0 lore raw

Right now, buildroot downloads sources from released tarball urls, it would be great if they could also pull from source repositories (git, svn, etc.) to get unreleased features. For example I ran into an issue with uclibc which was fixed but not yet released. It may also assist in weeding out integration issues before package release.

#1 lore raw

Le Thu, 7 Jul 2011 10:06:18 -0400,
James Hanley <[email protected]> a ?crit :

Quoted 5 lines

Right now, buildroot downloads sources from released tarball urls, it would be great if they could also pull from source repositories (git, svn, etc.) to get unreleased features. For example I ran into an issue with uclibc which was fixed but not yet released. It may also assist in weeding out integration issues before package release.

This is already implemented. In a package, you can do :

<pkg>_SITE = git://foobar.com/barfoo.git
<pkg>_SITE_METHOD = git
<pkg>_VERSION = some-git-tag-or-commit-id-or-branch

Same with Subversion and Bazaar.

Regards,

Thomas

Signature · 4 lines
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
#2 lore raw

Le Thu, 7 Jul 2011 16:19:43 +0200,
Thomas Petazzoni <[email protected]> a ?crit :

Quoted 7 lines

This is already implemented. In a package, you can do :

<pkg>_SITE = git://foobar.com/barfoo.git
<pkg>_SITE_METHOD = git
<pkg>_VERSION = some-git-tag-or-commit-id-or-branch

Same with Subversion and Bazaar.

I should probably have said that this wouldn't work with uClibc. This is due to the fact that uClibc is not a normal Buildroot package that relies on the common infrastructure. It's a very special component, built by its own Makefile.

However, we have an option to build an uClibc snapshot tarball. If you just tell Buildroot to do this, it will grab the latest daily tarball of uClibc. You can also tell Buildroot to select an arbitrary tarball, by date.

Regards,

Thomas

Signature · 4 lines
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
#3 lore raw
In reply to James Hanley
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"James" == James Hanley <[email protected]> writes:

James> Right now, buildroot downloads sources from released tarball urls, it James> would be great if they could also pull from source repositories (git, James> svn, etc.) to get unreleased features. For example I ran into an issue James> with uclibc which was fixed but not yet released. It may also assist James> in weeding out integration issues before package release.

I see Thomas already answered you, but what problem was this exactly and what uClibc git commit fixed it? Probably we can backport it to 0.9.32 and include it in buildroot.

Signature · 1 line
Bye, Peter Korsgaard
#4 lore raw

I meant to reply all - sorry Peter for the double message.

I used this patch
http://lists.uclibc.org/pipermail/uclibc-cvs/2011-June/029684.html
with some modification - specifically where he used int nsig = _NSIG / 8;
I used
const int nsig = _NSIG / 8;

Quoted 15 lines · Peter Korsgaard
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"James" == James Hanley <[email protected]> writes:

?James> Right now, buildroot downloads sources from released tarball urls, it ?James> would be great if they could also pull from source repositories (git, ?James> svn, etc.) to get unreleased features. For example I ran into an issue ?James> with uclibc which was fixed but not yet released. ?It may also assist ?James> in weeding out integration issues before package release.

I see Thomas already answered you, but what problem was this exactly and what uClibc git commit fixed it? Probably we can backport it to 0.9.32 and include it in buildroot.

--
Bye, Peter Korsgaard

#5 lore raw
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"James" == James Hanley <[email protected]> writes:

James> I meant to reply all - sorry Peter for the double message. James> I used this patch
James> http://lists.uclibc.org/pipermail/uclibc-cvs/2011-June/029684.html
James> with some modification - specifically where he used James> int nsig = _NSIG / 8;
James> I used
James> const int nsig = _NSIG / 8;

Ok, we have that one since Wednesday.

Signature · 1 line
Bye, Peter Korsgaard