All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFT][PATCH V2] eglibc-2.16: Use tar ball instead of svn SRC_URI
Date: Wed, 17 Oct 2012 22:28:49 +0100	[thread overview]
Message-ID: <1350509329.2185.136.camel@ted> (raw)
In-Reply-To: <CAP9ODKpprdTNmgJCZvir9jM7mnpS9RN17G_s=mbNW0RL4ZvQww@mail.gmail.com>

On Wed, 2012-10-17 at 17:42 -0300, Otavio Salvador wrote:
> On Wed, Oct 17, 2012 at 4:07 PM, Khem Raj <raj.khem@gmail.com> wrote:
>         Adapt the recipes to fetch a tarball.
>         Tarball is generated from latest 2.16 branch
>         which has e500-math_private.patch already applied
>         hence we remove that patch.
>
>         Signed-off-by: Khem Raj <raj.khem@gmail.com>
>
> What the motivation to move to the tarball?

svn:// recipes depend on subversion-native. Having switched to the new
ubversion version, we've in a nasty position of it being hard to
ASSUME_PROVIDED with the API breakage.

Building subversion-native is a pain and delays the core part of the
build significantly. Switching to tarball recipes should improve our
build speed a lot.

So its mainly for performance reasons that we should do this.

My only question is whether we need to include the svn revision in the
tarball name?

Cheers,

Richard






  reply	other threads:[~2012-10-17 21:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-17 19:07 [RFT][PATCH V2] eglibc-2.16: Use tar ball instead of svn SRC_URI Khem Raj
2012-10-17 20:42 ` Otavio Salvador
2012-10-17 21:28   ` Richard Purdie [this message]
2012-10-17 21:37     ` Khem Raj
2012-10-17 22:08     ` Otavio Salvador

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=1350509329.2185.136.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.