Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 00/14] Bitbake fetcher mirror handling overhaul
Date: Wed, 20 Jun 2012 15:12:51 +0100	[thread overview]
Message-ID: <cover.1340200207.git.richard.purdie@linuxfoundation.org> (raw)

The following commits overhaul bitbake's mirror handling in the fetcher
bring various correctness fixes and improvements.

Richard Purdie (14):
  fetch2/__init__: Make it clearer when uri_replace doesn't return a
    match
  fetch2: Fix error handling in uri_replace()
  fetch2: Only cache data if fn is set, its pointless caching it
    against a None value
  fetch2: Ensure when downloading we are consistently in the same
    directory
  fetch2: Split try_mirrors into two parts
  fetch2: Explicitly check for mirror tarballs in mirror handling code
  fetch2: Improve mirror looping to consider more cases
  fetch2: Simplify some looping constructs in uri_replace()
  fetch2: Remove basestring test and simplify uri_replace
  fetch2: Add parameter handling to uri_replace()
  fetch2: uri_replace() remove what amounts to a null operation and add
    some comments
  fetch2: uri_replace() improve mirrortarball handling
  fetch2: uri_replace() only consider ud.localpath where its a file
  test/fetch: Add in unit tests for uri_replace() and git premirrors

 bitbake/lib/bb/fetch2/__init__.py |  203 ++++++++++++++++++++++---------------
 bitbake/lib/bb/tests/fetch.py     |   55 ++++++++++-
 2 files changed, 175 insertions(+), 83 deletions(-)

-- 
1.7.5.4




             reply	other threads:[~2012-06-20 14:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 14:12 Richard Purdie [this message]
2012-06-20 14:12 ` [PATCH 01/14] fetch2/__init__: Make it clearer when uri_replace doesn't return a match Richard Purdie
2012-06-20 14:12 ` [PATCH 02/14] fetch2: Fix error handling in uri_replace() Richard Purdie
2012-06-20 14:12 ` [PATCH 03/14] fetch2: Only cache data if fn is set, its pointless caching it against a None value Richard Purdie
2012-06-20 14:12 ` [PATCH 04/14] fetch2: Ensure when downloading we are consistently in the same directory Richard Purdie
2012-06-20 14:12 ` [PATCH 05/14] fetch2: Split try_mirrors into two parts Richard Purdie
2012-06-20 14:12 ` [PATCH 06/14] fetch2: Explicitly check for mirror tarballs in mirror handling code Richard Purdie
2012-06-20 14:12 ` [PATCH 07/14] fetch2: Improve mirror looping to consider more cases Richard Purdie
2012-06-20 14:12 ` [PATCH 08/14] fetch2: Simplify some looping constructs in uri_replace() Richard Purdie
2012-06-20 14:13 ` [PATCH 09/14] fetch2: Remove basestring test and simplify uri_replace Richard Purdie
2012-06-20 14:13 ` [PATCH 10/14] fetch2: Add parameter handling to uri_replace() Richard Purdie
2012-06-20 14:13 ` [PATCH 11/14] fetch2: uri_replace() remove what amounts to a null operation and add some comments Richard Purdie
2012-06-20 14:13 ` [PATCH 12/14] fetch2: uri_replace() improve mirrortarball handling Richard Purdie
2012-06-20 14:13 ` [PATCH 13/14] fetch2: uri_replace() only consider ud.localpath where its a file Richard Purdie
2012-06-20 14:13 ` [PATCH 14/14] test/fetch: Add in unit tests for uri_replace() and git premirrors Richard Purdie

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=cover.1340200207.git.richard.purdie@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    /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