[Aboriginal] Build from version control system repos instead of from tarballs

Rob Landley rob at landley.net
Fri Oct 5 08:39:00 PDT 2012


Let's try that again actually cc:ing the list. (Not a fan of the gmail
web interface.
Need to fix my email...)

On Fri, Oct 5, 2012 at 9:47 AM, Alessio Igor Bogani
<alessioigorbogani at gmail.com> wrote:
> Hi Rob,
>
>
> On 09/09/2012 03:55, Rob Landley wrote:
>>
>> On 09/04/2012 03:49 AM, Alessio Igor Bogani wrote:
>>>
>>> Hi All,
>>>
>>> Can Aboriginal grabs sources from git(Linux, musl, uclibc, busybox)
>>> and hg(toybox) repos instead of from tarballs?
>>> Thanks!
>
> [...]
>
>> I'm thinking about ways to simplify the package cache dance I mentioned
>> earlier. Possibly the package cache should be packages/cache and then
>> the procedure should be:
>>
>> 1) comment out the tarball URL in download.sh
>> 2) remove the patches you don't want applied from sources/patches
>> 3) git clone packages/cache/thingy
>
>
> Unfortunately it doesn't work.
>
> I have tried with the linux kernel so I commented out download.sh lines in
> this way:
> #URL=http://www.kernel.org/pub/linux/kernel/v3.x/linux-3.5.tar.bz2 \
> #SHA1=d80e85147417605e125fc3fb263af85d7ffd1ad5 \
> #ALT=http://kernel.org/pub/linux/kernel/v3.0/testing/linux-3.0-rc1.tar.bz2 \
> #maybe_fork "download || dienow"
>
> Left sources/patches untouched.

Ah, sorry. I need to properly document this.

If you comment out the URL= and maybe_fork "download || dienow" bits,
it won't update the timestamp on the tarball in the packages
directory, and then cleanup_oldfiles will delete all files in there
that predate this run of download.sh (thinking they're old leftover
versions that are no longer used.)

(This only matters if you're putting an alt-tarball in the packages directory,
which it doesn't sound like you're doing.)

> Cloned linux git tree into packages/cache/linux

You mean build/packages/linux ?

I mentioned I was thinking about moving the package cache under the
"packages" directory rather than the "build" directory, but neither is
quite a good fit.  The build directory is all the generated files, so
you can "rm -rf build" and then re-run the build and that does a clean
build.

The "packages" directory is all the downloaded files that came from
somewhere other than this source repository. The download.sh script
populates that.

Whether the extracted and patched source is a better fit for "build"
(generated files) or "packages" (downloaded files) is an open
question.

> Do you have any suggestions?

mkdir -p build/packages
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux
build/packages/linux

Try that?

> Ciao,
> Alessio

 1349451540.0


More information about the Aboriginal mailing list