Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] git: add SRC_URI name
Date: Mon, 22 Feb 2010 20:41:59 +0100	[thread overview]
Message-ID: <20100222194159.GZ30265@mx.loc> (raw)
In-Reply-To: <20100222181754.GB24049@jama>

On Mon, Feb 22, 2010 at 07:17:54PM +0100, Martin Jansa wrote:
>On Mon, Feb 22, 2010 at 10:06:00AM -0700, Chris Larson wrote:
>> On Mon, Feb 22, 2010 at 9:55 AM, Phil Blundell <philb@gnu.org> wrote:
>> > On Mon, 2010-02-22 at 11:24 -0500, Denys Dmytriyenko wrote:
>> >> On Sun, Feb 21, 2010 at 04:32:32PM +0100, Bernhard Reutner-Fischer wrote:
>> >> > Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
>> >> > ---
>> >> >  recipes/git/git.inc |    2 +-
>> >> >  1 files changed, 1 insertions(+), 1 deletions(-)
>> >> >
>> >> > diff --git a/recipes/git/git.inc b/recipes/git/git.inc
>> >> > index 644e159..fd7b708 100644
>> >> > --- a/recipes/git/git.inc
>> >> > +++ b/recipes/git/git.inc
>> >> > @@ -2,7 +2,7 @@ DESCRIPTION = "The git revision control system used by the Linux kernel develope
>> >> >  SECTION = "console/utils"
>> >> >  LICENSE = "GPL"
>> >> >
>> >> > -SRC_URI = "http://www.kernel.org/pub/software/scm/git/git-${PV}.tar.bz2"
>> >> > +SRC_URI = "http://www.kernel.org/pub/software/scm/git/git-${PV}.tar.bz2;name=git"
>> >>
>> >> Is there a patch to add checksums in corresponding recipes to use the name? Or
>> >> what is the purpose of adding one?
>> >
>> > I guess the idea is to make it possible for new recipes (which use
>> > this .inc file) to include their own checksums.  Seems like a reasonable
>> > enough plan even if the old recipes are not converted.
>> 
>> Has anyone thought about programmatically injecting a name to the
>> first tarball/zip in the SRC_URI if no sources have that name yet?  It
>> seems like adding a name to the primary tarball is becoming common
>> boilerplate, and the common case is for that to be the first source.

For recipes that have only one fetched source, could we perhaps default
to plain SRC_URI[md5sum], without a name. If a second fetched source is
added, this would transparently break (i.e. require adding two names).
>
>Also would be great to have unified names where possible.

For recipes that have two or more fetched sources, i personally would
use PN but, as you say, that has the disadvantage that you have to
potentially lookup the package name in an .inc. Not my call though.

>It would make adding new recipes a bit easier (no need to
>check/copy&paster name used in .inc and also base.bbclass could easily
>generate those checksum sections with right name easier.
>
>I'm using "archive" as few others also used.

and some use tarball, some pn ....



  reply	other threads:[~2010-02-22 19:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-21 15:32 [PATCH] git: add SRC_URI name Bernhard Reutner-Fischer
2010-02-22 16:24 ` Denys Dmytriyenko
2010-02-22 16:55   ` Phil Blundell
2010-02-22 17:06     ` Chris Larson
2010-02-22 18:17       ` Martin Jansa
2010-02-22 19:41         ` Bernhard Reutner-Fischer [this message]
2010-02-22 21:43           ` Bernhard Reutner-Fischer
2010-02-22 22:06             ` Denys Dmytriyenko
2010-02-22 22:45               ` Bernhard Reutner-Fischer
2010-02-24 17:18                 ` Bernhard Reutner-Fischer
2010-03-05 20:53                   ` Bernhard Reutner-Fischer
2010-03-22 11:07                     ` Roman Khimov

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=20100222194159.GZ30265@mx.loc \
    --to=rep.dot.nop@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox