All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Javier Viguera <javier.viguera@digi.com>
Cc: "Tom King" <ka6sox@gmail.com>,
	"openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>,
	"Eric Bénard" <eric@eukrea.com>
Subject: Re: cherokee wrong SRC_URI (was Dylan backports)
Date: Thu, 07 Nov 2013 18:25:54 +0000	[thread overview]
Message-ID: <1606310.BaoZjjErcI@helios> (raw)
In-Reply-To: <527BCA0E.1070706@digi.com>

On Thursday 07 November 2013 18:12:46 Javier Viguera wrote:
> On 07/11/13 17:45, Paul Eggleton wrote:
> > 2) Longer term the recipe should just be upgraded; last I checked we've
> > fallen quite far behind the current version. Javier, if you're relying on
> > Cherokee is that something you'd be prepared to do?
> 
> The problem is not the version, the problem is the main cherokee project
> uses those github autogenerated-from-tags tarballs. See:
> 
> <http://cherokee-project.com/downloads.html>
> 
> Some examples:
> 
> <https://github.com/cherokee/webserver/archive/v1.2.103.zip>
> ...
> <https://github.com/cherokee/webserver/archive/v1.2.98.zip>
> 
> And as far as i know in this case we cannot rely the checksums remain
> stable.

This is something that would be worth trying to communicate upstream - these 
tarballs are just not useful as a release mechanism. Help them to understand 
that and we help ourselves.

> Anyway at this moment I'm stuck on Dylan working on a BSP layer, so I
> don't have the time to play with other branches, sorry.

OK, no problem.
 
> My preference at this moment would be to integrate the patch from Eric
> with the German mirror (once fixed in version 3) in all the branches and
> at the same time keep a copy of the tarball in one of the yoctoproject
> source mirrors.

It'll be the OpenEmbedded mirror in this instance, but yes.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


      reply	other threads:[~2013-11-07 18:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-10 15:55 Dylan backports Javier Viguera
2013-10-10 19:31 ` Eric Bénard
2013-11-07 14:50   ` Javier Viguera
2013-11-07 15:14     ` Eric Bénard
2013-11-07 16:02       ` cherokee wrong SRC_URI (was Dylan backports) Javier Viguera
2013-11-07 16:45         ` Paul Eggleton
2013-11-07 17:12           ` Javier Viguera
2013-11-07 18:25             ` Paul Eggleton [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=1606310.BaoZjjErcI@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=eric@eukrea.com \
    --cc=javier.viguera@digi.com \
    --cc=ka6sox@gmail.com \
    --cc=openembedded-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 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.